# More Accounts Partner API Sell LinkedIn profile subscriptions through your UI, a hosted page or an embed. More Accounts collects Stripe payments, supplies and operates profiles, applies approved changes, handles customer support and accounts for your agreed commission. **API v1:** `https://app.moreaccounts.com/api/partners/v1` **Reference:** [Swagger UI](https://app.moreaccounts.com/docs/) · [OpenAPI JSON](https://app.moreaccounts.com/docs/openapi.json). Coding agents: fetch the schema for exact request/response fields, constraints and examples. Its server is `https://app.moreaccounts.com`; its paths already include `/api/partners/v1`. ## Choose a mode and get access ### Who uses which interface? | Audience | Interface | What they manage | | --- | --- | --- | | Direct customer | More Accounts customer portal, `/portal/...` | Their own purchases, profile changes and requests; Billing, Team, Branding and Support use customer-team permissions. | | Partner customer, for example Dent | The same customer portal through a private hosted or embedded link | Only that company’s selection, checkout, purchases, profile changes, replies, period-end cancellation and manually enabled account access. | | Partner staff, for example Gelee or Sellable | Partner console, `/partner-console/{partner_id}/...`, or their server-side Partner API | Their own customers, orders, requests, private portal links, commission statements and settlement history. The console links to this reference and the OpenAPI schema. | | More Accounts | Ops | Internal integration settings, staff invitations, keys, commission terms, fulfillment, approvals, access grants and settlement administration. | The customer portal uses the same screens for normal sign-in and partner links. The entry mode determines authority: cookies never expand a private customer capability, and a partner link grants no customer-team or Ops membership. A partner-created customer gains normal sign-in access only through an explicit customer-team invitation, attached to that same record. New purchases retain the customer’s partner attribution regardless of entry point; historical orders and agreed commissions stay unchanged. The partner console has dedicated Customers, Orders, Requests, Statements and API & Documentation pages. More Accounts explicitly provisions its human operators. Operators cannot invite colleagues or administer integrations. Revoking a membership also invalidates customer links issued through it without resetting the person’s other memberships or password. The console uses human sign-in; API keys stay on the partner’s backend. Console operators can issue the same full customer links as the Partner API. Anyone holding such a link may perform its company-scoped operations, including handover after manual enablement and explicit acceptance. Disclosure checks and auditing still apply. The console itself does not display integration keys or account credentials. For example, Gelee creates Dent in the console and opens or shares Dent’s portal link. Dent manages its profiles in the shared portal; Gelee follows the order and requests in its console. Sellable has the same capabilities, subject to the same permissions. The public documentation links grant no additional authority. ### Partner branding Operators manage **Branding** and **Domains** in their own console. Branding is independent of the customer's company branding and LinkedIn banner settings. Upload a logo and a square icon, set the display name, button/background colors, support, privacy and terms links, and the customer email sender/reply-to. The preview preserves unsaved changes when visiting domain setup. The server rejects unsafe URLs, unsupported images and a button/background contrast below 3:1; text colors are chosen automatically for contrast. Logos are public PNG/JPEG images, normalized to remove embedded metadata, at most 512 KB. Icons must be square and at least 128 × 128 px. Historical images are retained for receipts. When enabled, the hosted and embedded customer screens use that identity, including page titles, favicons, support, legal links, unavailable-link screens and checkout. Customer-facing navigation does not display a More Accounts footer or our API documentation. The API reference remains prominent in the staff console. Native customers explicitly invited to the same customer record see the same brand after sign-in; their existing owner/member permissions remain intact. `GET /api/partners/v1/branding` returns the current public appearance, or `null` while branding is disabled. This read uses the partner's bearer key. Console changes use human-cookie endpoints under `/api/partner-console/{partner_id}/branding` and `/domains`; integration keys cannot authorize them. Public image and error-page identity endpoints return no customer data, account access, provider credentials or private object-store keys. Add a portal hostname (for example `profiles.vendor.com`) or an email sender domain (for example `mail.vendor.com`) in **Domains**. Publish the exact per-partner `_portal-verification` TXT record shown there, then check verification. Only after ownership is proven does the service request the hosting or sender records. Portal activation requires Vercel project ownership/configuration and a successful HTTPS application probe with a pinned public IP. Email activation requires the provider's verified domain status, including its DNS records. Saving a domain is not activation. Rechecks run every 12 hours; routing and mail fail closed after 24 hours without current verification. The first active portal domain supplies new links. Removing a portal domain or losing its ownership record revokes capabilities issued on that domain, preserving canonical-host and unrelated partner sessions. Removing an email domain does not delete provider mailboxes. Custom domains carry partner-issued, company-scoped customer links. Native human sign-in and invitations stay on the canonical customer host, so a partner domain never receives a person's session for unrelated customer teams. Human sessions are not shared across domains. Embed origin approval, staff revocation, manual handover grants and all existing authorization checks continue to apply. **Payments retain the existing collector and commission model.** Checkout receives a frozen partner name, colors, logo/icon and profile description for each new intent; uncertain retries reuse that snapshot. Its dedicated Stripe product preserves the base product's tax code, statement descriptor and unit label. Fulfillment still requires the exact frozen product, price, currency and quantity. Payments are still collected by More Accounts. Stripe-generated receipts, invoices and required legal merchant information retain that account's identity; checkout customization does not rebrand Stripe invoices. No Stripe account-wide branding is changed and no Connect transfers or destination charges are introduced. See [Stripe Checkout appearance](https://docs.stripe.com/payments/checkout/customization/appearance) and [Stripe receipts](https://docs.stripe.com/receipts). Paid purchase projections include `receipts`, created only after reconciled Stripe cash evidence. Each portal receipt preserves its original brand, amount, tax, currency, merchant and payment time, with refund totals shown separately. Customers can print/save the receipt. An idempotent customer email links to the receipt's purchase. Unverified senders wait in the encrypted email ledger; they never fall back to a More Accounts sender. Expired access links are suppressed instead of being mailed. Customer invitations, sign-in, profile setup, account-online and billing notifications use the applicable partner identity; sourcing, participant and workforce mail keep their existing identity. Existing customer template settings and required service copy remain in effect. Platform setup: configure server-only `PARTNER_VERCEL_TOKEN`, `PARTNER_VERCEL_PROJECT_ID` and optional `PARTNER_VERCEL_TEAM_ID` for the existing customer web project. The scoped token needs project-domain read/write and domain configuration read. PostStack needs `domains:read` and `domains:manage` in addition to existing email permissions. Keep `RECEIPT_MERCHANT_NAME` equal to the actual current payment collector. These settings and tokens are never sent to the browser. Provider references: [Vercel custom domains](https://vercel.com/docs/domains/working-with-domains/add-a-domain), [PostStack domain API](https://poststack.dev/openapi.json). ### Integration modes | Mode | Your implementation | | --- | --- | | Hosted | Bind the company, create a session and redirect to the returned URL. More Accounts provides the customer UI. | | Embedded | Create an embedded session for an approved origin and display the returned URL in an iframe. | | Own UI | Build catalogue, cart, checkout handoff, status and service screens; receive signed webhooks. | Every partner can use managed profile changes and optional direct account access. These capabilities are independent of vendor names and presentation mode. Account access still requires the explicit per-profile Owner grant described below. ### Customer pages Customer pages and the partner console run on the existing customer application host (`app.moreaccounts.com`, or the configured isolated preview host), separate from Ops. Each function has its own URL. The session fragment follows internal navigation; reloads, copied links and browser Back work within the same customer capability. Private links must never enter logs or analytics. Stored capabilities are removed from the visible URL; if tab storage is blocked the private fragment remains the recovery mechanism. Normal customer sign-in uses `/portal/purchases`, `/portal/requests`, `/portal/billing`, `/portal/team`, `/portal/branding` and `/portal/support`. Company owners also have `/portal/integrations` and `/portal/webhooks`. Existing Settings links open Branding. From Change requests, choose **New request** and select an eligible profile. “Buy profiles” opens the existing `/profiles` storefront with the selected customer preserved, including when the owner belongs to several companies. `/portal/catalog` redirects there; historical cart/editor/checkout links remain compatible. Ordinary customer members retain read-only permissions. Existing root/tab, setup, guest checkout and invitation URLs remain compatible. Partner-issued links retain these paths: | Function | Customer-portal path | | --- | --- | | Catalogue | `/partner/catalog` | | Cart and payment consent | `/partner/cart` | | Initial profile editor | `/partner/cart/profiles/{line_id}` | | Checkout status and recovery | `/partner/checkout/{order_id}` | | Purchases | `/partner/purchases` | | Individual purchase | `/partner/purchases/{order_id}` | | Managed profile editor | `/partner/purchases/{order_id}/profiles/{line_id}/edit` | | Optional account handover/access | `/partner/purchases/{order_id}/profiles/{line_id}/access` | | Period-end cancellation | `/partner/purchases/{order_id}/profiles/{line_id}/cancel` | | Change requests and replies | `/partner/requests`, `/partner/requests/new` and `/partner/requests/{request_id}` | Embedded pages use the same functions below their returned `/api/partner-pages/frames/{session_id}` base path, with the same capability, expiry and exact-origin frame policy. Existing root customer links still open the catalogue, and Stripe returns open the corresponding purchase. Internal partner administration, Owner grants and operational fulfillment remain in Ops; customers never need an Ops login. Obtain an enabled integration, server-side API key, agreed commission terms, support contact and approved test environment/inventory from More Accounts. Own-UI integrations also need fixed HTTPS success, cancellation and webhook URLs plus a webhook signing secret. Embeds need each exact parent origin registered. Hosted-only integrations need neither external checkout callbacks nor a webhook receiver. Coding agents should reuse the vendor's backend, authentication, company authorization and secret store. Ask for missing inputs and work with mocks until they are supplied. A sandbox is not implied; test cards, real purchases, payouts and commercial activation require the agreed test/launch procedure. ## Authentication and retries - Send `Authorization: Bearer ` on every request. Keep this key and webhook secrets on your server; browsers/mobile clients call your authorized backend. Cookies and customer-session tokens do not authorize partner API calls. - Authorize the signed-in user's company on your server. Company references are partner-scoped; matching emails never grant access to another team. - Every `POST`, `PUT` and `DELETE`, including uploads/reconciliation, requires `Idempotency-Key` (8–200 characters) and `X-Partner-Actor` (1–160 characters). - Persist the logical command before sending it. After a timeout or uncertain response, retry the same method, path, body, actor and key. A changed intent needs a new key. A replay may return an old result; use read/reconcile endpoints for current state. - Keep private links and secrets out of browser bundles, agent prompts, URLs, analytics and logs. API responses use `Cache-Control: no-store`. Use the public partner contract, not internal browser or operator routes. ## Hosted quickstart Run on your backend with an authorized company reference and a key from your secret store. Example identities are placeholders. ```bash export API_BASE='https://app.moreaccounts.com/api/partners/v1' export PARTNER_KEY='' curl --fail-with-body "$API_BASE/customers/company-123" --request PUT \ --header "Authorization: Bearer $PARTNER_KEY" \ --header 'Content-Type: application/json' \ --header 'Idempotency-Key: company-123-bind-001' \ --header 'X-Partner-Actor: user-456' \ --data '{"company":"Example Company","owner_name":"Alex Example","owner_email":"alex@example.com","business_brief":"Professional consulting services."}' curl --fail-with-body "$API_BASE/customers/company-123/sessions" --request POST \ --header "Authorization: Bearer $PARTNER_KEY" \ --header 'Content-Type: application/json' \ --header 'Idempotency-Key: company-123-session-001' \ --header 'X-Partner-Actor: user-456' \ --data '{"mode":"hosted"}' ``` Company fields above are required; `business_brief` is 10–4000 characters. Optional `website` must be public HTTPS. Session responses contain `id`, `url`, `mode` and `expires_at`. Redirect the authorized customer to `url` exactly as returned, retaining its fragment. The session is a private capability for one company, valid for two hours. It does not itself establish purchase consent or charge a payment. Use a fresh logical command for a new link after expiry/revocation. Revocation, integration/page disabling and API-key rotation block existing sessions; rotation permanently revokes them. ## Embedded page Create the same session with `{"mode":"embedded","parent_origin":"https://app.your-company.example"}`. The origin must exactly match a registered HTTPS origin; paths, wildcards, private IP literals and custom ports are refused. Removing an allowed origin blocks its embedded sessions. ```html ``` Allow `https://app.moreaccounts.com` in your `frame-src`; our response restricts `frame-ancestors` to the registered origin. Ask More Accounts about additional ancestor frames. Payment opens outside the iframe and returns to a top-level customer page. For optional resizing, accept `event.data.type === "moreaccounts.resize"` only when `event.origin` is `https://app.moreaccounts.com`, `event.source` is the iframe's window, `session_id` matches and `height` is finite. Clamp height to 320–12000. Messages never prove payment. Preserve the URL fragment; the page supports blocked tab storage and does not require third-party cookies. ## Endpoints Paths below are relative to the API base. Use the schema for exact payloads and response types. | Method | Path | Purpose | | --- | --- | --- | | PUT | `/customers/{customer_ref}` | Create/update company binding | | POST | `/customers/{customer_ref}/sessions` | Create hosted/embedded link | | DELETE | `/customers/{customer_ref}/sessions/{session_id}` | Revoke link | | GET | `/catalog` | List eligible inventory | | GET | `/customers/{customer_ref}/cart` | Resume cart/checkout | | POST | `/customers/{customer_ref}/cart/items` | Reserve `{"profile_id":""}` | | DELETE | `/customers/{customer_ref}/cart/items/{line_id}` | Remove unpaid selection | | POST | `/customers/{customer_ref}/checkout` | Start Stripe checkout | | POST | `/customers/{customer_ref}/checkout/cancel` | Cancel an unpaid checkout | | GET | `/customers/{customer_ref}/purchases` | List paid purchases | | GET | `/customers/{customer_ref}/purchases/{order_id}` | Read purchase/service status | | POST | `/customers/{customer_ref}/purchases/{order_id}/reconcile` | Reconcile payment state | | POST | `/customers/{customer_ref}/purchases/{order_id}/profiles/{line_id}/cancel` | Schedule one profile's period-end cancellation | | GET | `/customers/{customer_ref}/purchases/{order_id}/profiles/{line_id}/replacement-options` | Cached replacements for a definitively unavailable paid profile | | POST | `/customers/{customer_ref}/purchases/{order_id}/profiles/{line_id}/replacement` | Choose `{"inventory_id":""}` at the original recurring price | | POST | `/customers/{customer_ref}/purchases/{order_id}/profiles/{line_id}/refund` | Record the customer's refund choice; processing continues in the background | | POST | `/customers/{customer_ref}/assets` | Upload private banner; multipart field `file` | | GET | `/customers/{customer_ref}/assets/{asset_id}` | Read this company's banner | | POST | `/customers/{customer_ref}/change-requests` | Request permitted changes for `line_id` | | GET | `/customers/{customer_ref}/change-requests` | List change requests | | GET | `/customers/{customer_ref}/change-requests/{request_id}` | Read request and follow-up | | POST | `/customers/{customer_ref}/change-requests/{request_id}/replies` | Reply with `message` and optional `changes` | | GET | `/commissions` | Commission totals and invoice entries | | GET | `/settlements` | Recorded manual payments, including voids | ### Cart and payment rules - The catalogue accepts `page` (default 1), `page_size` (default 25, max 100), `country`, `location`, `verification`, `verified` and `min_connections`. Use `country` for an exact structured country match. Use `location` to search city, region, country and full supplier location text. Both ignore case. A connection range meets the minimum when its lower bound meets it. - The `verified` response field is `true` for confirmed verification, `false` for explicitly reported absence and `null` for unknown. New catalogue selections require a verification result and an exact connection count or reported range. An individual result takes precedence over a supplier-wide verification guarantee. Both zero connections and explicit non-verification qualify. The compatibility filter `?verified=unknown` returns an empty catalogue. Historical purchase snapshots can still contain unknown values. The separate `verification` filter matches the returned method exactly. The value `supplier` means the supplier confirmed verification without specifying a method. - Display `location` when present. It preserves the supplier’s full location text. Otherwise, use the supplied city, region and country. Older AllProfiles integrations can still read the full text from `region`. - Eligible inventory excludes warming, unavailable, reserved and assigned profiles. It includes authorized supplier offers marked `delivery_state: "confirming"`. More Accounts refreshes supplier stock every minute; listing and payment preparation use its local cache. Stock can change before the supplier purchase. Purchases contain 1–100 exact profiles with mixed prices. - Inventory `profile.id`/`profile_id` differs from cart `lines[].id`. Use the returned **line ID** for removal, later changes and cancellation. An empty cart has `id: null` and `lines: []`. - Shopping holds last 15 minutes; checkout holds are about 30 minutes. Server deadlines, prices and discounts are authoritative. Checkout freezes selection: resume it or confirm cancellation before editing. - Collect consent before checkout. Body: `{"consent":true,"permitted_activities":["connect"]}`. Send only customer-approved activities from `connect`, `post`, `like`, `repost`, `comment`; at least one is required. Optional `initial_changes` has at most one configuration per selected `inventory_id`. Never submit your own price or commission. - Redirect to returned `checkout_url`. Own-UI returns use registered callbacks and `moreaccounts_order_id`. A Stripe return or frame message is **not payment/readiness proof**: read/reconcile `paid`, `needs_ops_review` and per-line `service_state`. Paid profiles may still be `configuring` or need attention. Render future states without crashing. - Preserve checkout idempotency after timeout/503. An unpaid cancellation can race with payment; if payment wins, continue the paid workflow. Paid profile cancellation takes effect at period end, without an automatic refund, immediate inventory release or cancellation of other lines. More Accounts handles refunds and replacements. - After payment, supplier lines report `fulfillment_state` and a `service_state` such as `confirming_profile`, `choose_replacement`, `refund_pending` or `refunded`. When `replacement_required` is true, ask the customer to choose from replacement options or request a refund if `refund_available`. Never select a substitute automatically. Both mutations require the normal command headers and exact company/order/line binding. A replacement preserves the paid slot and monthly price. A refund stops future renewal for that slot and returns its share of the original collected payment; show pending until confirmed. All supplier I/O is performed server-side by More Accounts. A paid supplier selection accepts branding during fulfillment. Read the line’s `allowed_change_fields` and submit its `line_id` to the existing change-request endpoint. A customer can revise an unclaimed supplier branding request. Taskforce verifies the requested fields after delivery. Report an observed restriction on an assigned supplier profile with `POST /customers/{customer_ref}/purchases/{order_id}/profiles/{line_id}/restriction`, the usual mutation headers and an `observation` string of up to 500 characters. Repeated reports on that paid selection share the case. The line’s `restriction` field exposes the case status and any recorded decision. Decisions for a refund or replacement keep the case open for evidence of the separately authorized outcome. A company status integration can receive `profile_restriction.updated` with the order ID, line ID, status and decision. Partner integrations receive the updated purchase through their existing purchase events. ### Profile changes and support The profile name, location and photo are read-only. Use each line’s `current_profile` to show its recorded headline, About, images, Experience and Education. Missing values are unknown. Load private images from the customer-scoped assets endpoint. Use `initial_change_fields` for cart lines, `allowed_change_fields` for purchased lines and the request’s `allowed_change_fields` when revising a request. Participant-owned accounts permit only headline, About and banner changes under their agreement. Other eligible individual profiles also support Experience, Education, Reposts and Featured links. | Allowed field | Request value | | --- | --- | | `headline` | A professional headline of 1–220 characters. | | `about` | Up to 2,600 characters. An empty string clears About. | | `banner` | Upload a PNG, JPEG or WebP image of up to 8 MB. Send its customer-bound ID as `banner_asset_id`. | | `experience` | Up to 12 positions, newest first. Each has `title`, `company` and `started_on` (YYYY-MM). `ended_on` and `summary` are optional. | | `education` | Up to 6 entries. Each has `school` and optional `degree`, `field_of_study`, `started_year` and `ended_year`. | | `reposts` | One to three distinct canonical LinkedIn post URLs, without tracking parameters. Repost without commentary; preserve older activity and skip posts already reposted. Requires current repost permission and account activity limits. | | `featured` | Up to ten distinct public HTTPS links in display order. Replaces Featured; an empty array explicitly clears it. | Reposts and Featured are per-profile requests, not company defaults. Submission is not completion: Ops applies the requested content and verifies it. The recorded Reposts list reflects the last verified request, not a live activity feed. Send at least one change. Omit sections you want to keep. A supplied history replaces that entire section, and an empty array clears it. For example, `{"line_id":"","education":[{"school":"School of Design","degree":"BA"}]}` requests one education entry and preserves the person’s Experience. Request states: `submitted`, `in_progress`, `needs_information`, `completed`, `failed`, `cancelled`. Display `message`, `messages` and `next_step`. For `needs_information`, reply with a non-empty `message` (max 4000 characters) and optional `changes`. Preserve customer input and provide the agreed More Accounts support contact. Every partner can submit profile changes through the same API and customer pages. More Accounts can assign each partner's profile changes to a specific active Taskforce operator, including an external browser agent such as Grokbot. Every assignment follows the normal Ops checklist, account lease and read-only verification. Submitting a change or an operator reporting completion does not prove that it was applied. Only verified successful changes update `current_profile`. ### Company branding and individual overrides Customer owners manage the company logo, banner, brand files and guidance in Branding. Brand files, logos and guidance are reference material for Ops; they do not authorize changes to names, portraits or unrequested profile fields. New requests keep a private snapshot of their brand references without changing approved ticket specifications. Assigned fulfillers and authorized internal reviewers can download those exact references, even when the customer later removes them from the active kit. Customer owners edit the default headline and About directly on the company profile preview under **Branding → Company defaults**. The company name, website and logo are under **Brand references**. Each profile’s Experience and Education belong to that individual. New managed purchases freeze the defaults at checkout. For existing managed profiles, the service submits inherited changes for review when the profile can accept a request. A personal value submitted at checkout, in a change request, or in a revision overrides only that field. An explicitly empty About is an individual override. Removing a company default stops future updates for that field and leaves recorded text in place. Each managed purchase line exposes `text_branding.headline` and `text_branding.about`, each with `source` (`company` or `custom`) and the current `company_value`. The recorded text is in `current_profile`. Requests generated from company text have `source: "company_defaults"`. A company owner can return either individual field to its default in the profile’s Branding editor. Uploading a company banner sets the default for future purchases. Existing profiles change only after the owner reviews the affected list and submits normal profile-change requests. Profiles with custom banners, open requests or unavailable managed changes are excluded. Removing the default does not remove applied banners, queued changes or historical assets. Owners can explicitly activate a previously saved company banner; existing custom banners are preserved. Purchase lines return `banner_source` (`company` or `custom`) and `company_banner_asset_id`. A custom banner supplied at checkout, in a change request or in a reply overrides the company default. Checkout freezes the chosen default; later company edits do not rewrite a paid order's initial configuration. Use `POST /customers/{customer_ref}/purchases/{order_id}/profiles/{line_id}/banner-preference` with `{"source":"custom"}` to keep the current banner outside company-wide updates, or `{"source":"company"}` to follow the company banner again. This uses the usual actor and idempotency headers. The response contains `banner_source` and an optional `request`: returning to a different company banner creates a request subject to ordinary approval, execution and independent verification. An open request blocks preference changes. Partner links and API keys do not acquire company Branding, Support setup, Billing or Team privileges. Requests also return `profile_name`, `created_at` and `source` (`profile` or `company_banner`) for profile-specific inboxes and conversations. Company headline and About defaults accept `{first_name}`, `{full_name}` and `{company}`. The service personalizes each profile separately and freezes paid checkout values. The individual editor inserts the selected profile’s value. Owners can also copy another profile’s recorded custom headline, About text and uploaded banner into a draft in the same company. They can edit the draft before submitting it through the usual review. ### Sequencer connections Each paid purchase line includes `connections`. An empty list means the portal has no recorded sequencer connection for that profile. A signed-in customer can report a disconnect under **Your profiles → Manage → Report a disconnect**. Partner backends can submit the same report to `POST /customers/{customer_ref}/purchases/{order_id}/profiles/{line_id}/disconnects` with the standard command headers and a body such as `{"sequencer":"HeyReach","note":"The sender is showing as disconnected."}`. Repeated reports for the same incident return the existing ticket. A connection exposes its ID, order and line IDs, sequencer, connection status, source, observation time, and support ticket ID, status and portal path. Ticket states are `reported`, `in_progress` and `resolved`. The portal shows “We’re on it” after Ops starts the ticket. A linked sender needs a confirmed connection from its sequencer to resolve the incident. For a manually reported tool, Ops records what it verified. Partners can receive `profile_connection.updated` and recover current state through the normal purchase read. In the customer portal, company owners can open **Webhooks** to register a public HTTPS endpoint, copy its signing secret, send a test and check the last delivery. Customer webhooks use the same signed envelope, signature headers and retry schedule as partner webhooks. The test event is `status.test`. Changing the endpoint rotates its secret and retires pending deliveries for the old endpoint. For a read-only API key, open **Integrations → Read-only status API**. Use the key as a Bearer token on `GET /api/status/v1/connections` on the customer portal origin. Optional parameters are `line_id`, `offset` and `limit` (1–100). To monitor senders automatically, an owner saves the company’s credentials under **Integrations → Sequencers**, then opens **Your profiles → Sequencer connection → Monitor a sender**. On a profile with no previous reports, the menu entry is **Report a disconnect**. Each tool can monitor the same profile independently. | Sequencer | Credentials and sender ID | Connection check | | --- | --- | --- | | HeyReach | Workspace API key and numeric sender ID | Reads the sender’s connected or disconnected state. [HeyReach sender status](https://docs.heyreach.io/hey-reach-api/linked-in-accounts/get-account-status) | | lemlist | Team API key and user ID starting with `usr_` | Matches the recorded LinkedIn URL and reads the user’s LinkedIn channel status. A different LinkedIn URL on the same user ID requires checking the link. [lemlist Get User](https://developer.lemlist.com/api-reference/endpoints/users/get-user) | | Expandi | Open API key, API secret, and numeric LinkedIn account ID | Matches the ID and profile name in the account list, then reads the account’s login status. An explicit sign-in challenge opens a ticket. [Expandi Open API](https://api.liaufa.com/open-swagger/) | | Gelee | Read-only workspace key and seat ID | Reads the selected seat’s LinkedIn URL and `connected` flag from `GET /me`. [Gelee workspace API](https://www.gelee.ai/docs) | | Aimfox | Regular workspace key and numeric account ID | Matches the LinkedIn public identifier. The account list confirms a logged-in session. Login and logout events report changes to the linked account. [Aimfox API and webhooks](https://docs.aimfox.com/) | | La Growth Machine | Workspace API key and identity ID | Matches the identity by ID and unique profile name, then reads its `linkedinConnected` flag. [La Growth Machine identities](https://developers.lagrowthmachine.com/agents/endpoints/#get-identities) | | Skylead | Workspace API key and numeric seat ID | Matches the seat ID and unique profile name in the visible seats. Its authentication state confirms recovery or a login problem. A seat missing from the list keeps its last observation. [Skylead API reference](https://documenter.getpostman.com/view/7428744/UV5ZAGMg) | | Salesflow | Public API bearer key and numeric account ID | Verifies the account’s own LinkedIn profile when linking, then reads its login state and account status. [Salesflow account API](https://salesflow.apidocumentation.com/api-reference) | | SalesRobot | API key and LinkedIn account UUID | Checks the matching LinkedIn URL, account health, session expiry and whether the account requires reconnection. [SalesRobot API reference](https://documenter.getpostman.com/view/10815846/2sB3BKE8Fb) | For Aimfox, choose **Set up login webhooks** after saving the key. In the Aimfox workspace’s webhook settings, paste the URL and set the `Authorization` header to the value shown. Subscribe to both `account_logged_in` and `account_logged_out`. Replacing the workspace key also changes the webhook credential. The portal accepts events only for the bound company, workspace, sender and LinkedIn profile. [Aimfox webhook setup](https://docs.aimfox.com/) Scheduled checks run about five minutes apart. An unavailable API or inconclusive result preserves the last observation and any open ticket. Replacing or removing credentials unlinks only that tool’s senders. Customers can select all 16 tools on the [More Accounts compatibility page](https://moreaccounts.com/#works-with) under **Report a disconnect**. Seven currently use manual reports and Ops-confirmed recovery. Their public integration references cover the following: | Tool | Published integration | | --- | --- | | Dripify | Team-member activity, campaign statistics and leads. [Dripify Open API](https://api.dripify.com/) | | Waalaxy | API-key validity and permissions, campaigns and imports. [Waalaxy connection check](https://docs.waalaxy.com/api/connection) | | Linked Helper | Sends prospect data from campaign steps. [Linked Helper webhooks](https://support.linkedhelper.com/hc/en-us/articles/360016687659-Send-person-to-webhook) | | Meet Alfred | Webhooks for leads and campaign activity. [Meet Alfred webhooks](https://help.meetalfred.com/en/articles/8346318-meet-alfred-webhooks-integration) | | We-Connect | The account API returns basic account details. The OAuth-based MCP also offers account-health reports. A LinkedIn session field for automatic polling still needs verification. [We-Connect account API](https://apidoc.we-connect.io/get-account-details) · [We-Connect MCP](https://we-connect.io/linkedin-mcp) | | Closely | Contact updates, tags, notes and replies. [Closely webhooks](https://help.closelyhq.com/en/articles/7470856-webhooks-integration) | | Octopus CRM | Campaign actions and data exports to other tools. [Octopus CRM integrations](https://octopuscrm.io/) | ### Optional direct account access Optional direct access is available to every partner under the same rules; it is not tied to a vendor name. Direct access is disabled for every newly assigned profile. A More Accounts Owner must enable it for the individual managed profile after configuration is complete. Participant-owned supply cannot receive this access. Every partner can display the returned `customer_access_enabled` flag; paid purchase status alone grants no account access. Managed profile changes continue through the change-request API while direct access is disabled. For a purchased line use `/customers/{customer_ref}/purchases/{order_id}/profiles/{line_id}/access`: | Method | Suffix | Purpose | | --- | --- | --- | | GET | none | Read current handover readiness | | POST | `/accept` | Accept handover after showing its consequences | | POST | `/reveal` | Reveal the existing LinkedIn sign-in and dedicated proxy after acceptance | | POST | `/totp` | Obtain a short-lived sign-in code | The POST routes require the normal mutation headers. Reveals and codes are generated fresh and are never stored in idempotency responses. Keep them in memory only, outside logs, analytics and persistent storage. Recovery mailbox credentials and the permanent authenticator seed remain managed. The API rechecks the exact customer, purchase, active paid line, account-work lease and Owner grant for every operation. Revocation, reassignment, ended access or an unpaid subscription blocks further disclosure. Hosted and embedded customer pages expose the same flow only after manual enablement. Profile changes are no longer accepted once handover begins. ## Webhooks Own-UI integrations use webhooks plus read endpoints for recovery. Events include `purchase.updated`, `change_request.updated`, `profile_connection.updated`, `commission.updated` and `settlement.updated`. Envelope: `{id,type,version,created_at,data}`; resource ID is `data.id`, and data is the resource's full public representation. Verify `X-Partner-Signature: t=,v1=` with the **webhook signing secret**, over `timestamp + "." + raw_body_bytes`, before JSON parsing. Reject timestamps outside ±5 minutes; compare digests in constant time. The tested verifier is below. Durably deduplicate by the signed body's `id`, validate fields, acknowledge with `2xx`, then process asynchronously. `X-Partner-Event-Id` is diagnostic, not trusted identity. Apply newer versions per `(event type, data.id)`: the counter is partner-wide, so gaps are normal. Recover missed events through reads. Retries: 1m, 5m, 15m, 1h, 6h; after six failed attempts ask More Accounts to repair/replay. Replays retain the event ID. ## Commissions Checkout snapshots the agreed rate for that subscription and its renewals. Basis: verified Stripe-collected subscription cash after discounts, attributable tax, successful refunds and lost disputes, before Stripe processing fees. Pending disputes hold commission; zero-cash and outside-Stripe paid invoices earn none. Supplier compensation is separate. All money is integer USD cents; `1250` basis points means 12.5%. `commission_cents` is lifetime net commission; `held_cents` is held for disputes. `available_cents = commission_cents - held_cents` **before receipts**. `settled_cents` is unvoided recorded payments; `outstanding_cents = available_cents - settled_cents`. Negative balances are valid. Recording/voiding a receipt never initiates/reverses a transfer; vendors cannot trigger payouts. ## Errors, pagination and acceptance Catalogue and statements return `{items,total,page,page_size}`; purchase/change-request lists return arrays. Lists accept `page` and `page_size` (max 100); check schema defaults per endpoint. Statement totals cover all history, not just the page. | Status | Recovery | | --- | --- | | 400 / 422 | Correct the request or validation details | | 401 / 403 | Check credentials, session expiry and approved integration configuration | | 404 | Resource unavailable in this company/partner scope | | 409 | Refresh conflicting state or fix idempotency reuse; new intent needs a new key | | 429 / 5xx / network uncertainty | Bounded backoff, honor `Retry-After`; retain mutation key, read/reconcile before starting another checkout | Errors normally contain `detail` as a string or validation array. Preserve input and show an actionable next step. Do not promise a quota or response-time SLA. Before launch, prove company isolation, expired/revoked sessions, embed origin checks, blocked tab storage, explicit consent, stable retries, server pricing/expiry, paid-but-configuring states, profile follow-ups, cancellation timing, signed/deduplicated/ordered webhooks and correct commission balances. Use only approved test context. Handoff: code changes, checks, required secret names/URLs and missing inputs; distinguish mocks from real transactions and deployment from commercial activation. ## Webhook verification example Node.js 22+, no dependencies. ```js import { createHmac, timingSafeEqual } from 'node:crypto'; /** Verify a raw-body Buffer before JSON parsing. Node.js 22+; no dependencies. */ export function verifyPartnerWebhook(rawBody, signature, secret, nowSeconds = Math.floor(Date.now() / 1000)) { if (!Buffer.isBuffer(rawBody) || typeof signature !== 'string' || typeof secret !== 'string' || !secret) return false; const fields = signature.split(',').map(part => part.split('=')); if (fields.length !== 2 || fields.some(part => part.length !== 2)) return false; const values = new Map(fields); if (values.size !== 2 || !values.has('t') || !values.has('v1')) return false; const timestamp = values.get('t'); const seconds = Number(timestamp); if (!Number.isSafeInteger(seconds) || String(seconds) !== timestamp || Math.abs(nowSeconds - seconds) > 300) return false; const digest = values.get('v1'); if (digest.length !== 64) return false; const received = Buffer.from(digest, 'hex'); const expected = createHmac('sha256', secret).update(timestamp).update('.').update(rawBody).digest(); return received.length === expected.length && timingSafeEqual(received, expected); } /* Framework-neutral request handling: const rawBody = Buffer.from(await request.arrayBuffer()); if (!verifyPartnerWebhook(rawBody, request.headers.get('X-Partner-Signature'), webhookSecret)) { return new Response('Invalid signature', { status: 401 }); } const event = JSON.parse(rawBody.toString('utf8')); // Validate event.id/type/version/data.id. Persist verified receipt with a unique // event.id constraint, acknowledge with 2xx, then process asynchronously. // Update a resource only when event.version is newer for (event.type, data.id). // Handle duplicates with 2xx. Do not use the unsigned event-ID header for trust. */ ```