Skip to content

Mercury: List recipient invites

Mercury recipientInvites.listRecipientInvites: arguments, response, policy and SDK examples.

← Recipient invites operations · Get started

Operation mercury.listrecipientinvites

Provider route: GET /recipients/invites. Alter supplies the connection’s credentials and routing.

Install @alter-ai/sdk @alter-ai/mercury with npm, or alter-sdk-mercury with pip. Supply your connected customer’s grant ID and the arguments described below.

import { App } from "@alter-ai/sdk";
import { MercuryIntegration } from "@alter-ai/mercury";
async function execute(input: Parameters<MercuryIntegration["recipientInvites"]["listRecipientInvites"]>[0]) {
const app = new App({ apiKey: process.env.ALTER_API_KEY! });
try {
const provider = new MercuryIntegration(app, { grantId: process.env.PROVIDER_GRANT_ID! });
const call = await provider.recipientInvites.listRecipientInvites(input);
const result = await call.wait();
return result.bodyJson();
} finally {
await app.close();
}
}
import os
from alter_sdk import App
from alter_sdk_mercury import MercuryIntegration
async def execute(arguments):
async with App(api_key=os.environ["ALTER_API_KEY"]) as app:
provider = MercuryIntegration(app, {"grant_id": os.environ["PROVIDER_GRANT_ID"]})
call = await provider.recipient_invites.list_recipient_invites(arguments)
result = await call.wait()
return result.body_json()
FieldTypePresenceDescription and constraints
$objectRootAdditional keys: not allowed
queryobjectOptionalAdditional keys: not allowed
query.limitintegerOptionalMaximum number of results to return. Allowed range: 1 to 1000. Defaults to 1000
Default: 1000
Format: int64
Maximum: 1000
Minimum: 1
query.start_afterstringOptionalThe ID of the recipient invite to start the page after (exclusive). When provided, results will begin with the recipient invite immediately following this ID. Use this for standard forward pagination to get the next page of results. Cannot be combined with end_before.
query.end_beforestringOptionalThe ID of the recipient invite to end the page before (exclusive). When provided, results will end just before this ID and work backwards. Use this for reverse pagination or to retrieve previous pages. Cannot be combined with start_after.
query.orderstringOptionalSort order. Can be ‘asc’ or ‘desc’. Defaults to ‘asc’
Default: asc
One of: asc, desc
query.statusstringOptionalOne of: created, completed, expired, declined

Response media type: application/json. The table describes the pinned successful response. Referenced models link to their complete fields.

FieldTypePresenceDescription and constraints
$ModelRootExpand List recipient invites — response body

Referenced models: List recipient invites — response body

List recipient invites — response body
FieldTypePresenceDescription and constraints
$objectRootAPI response for listing recipient invites with pagination.
invitesarrayRequired within parentList of invites in the current page.
invites[]ModelEach itemExpand Create a recipient invite — response body
pageobjectRequired within parentPagination cursors (inviteId) for navigating to next/previous pages.
page.nextPagestringOptionalID for the invite
page.previousPagestringOptionalID for the invite

Referenced models: Create a recipient invite — response body

Create a recipient invite — response body
FieldTypePresenceDescription and constraints
$objectRoot
contactEmailJSONRequired within parent
contactEmail (allOf 1)stringAll variants apply
contactEmail (allOf 2)JSONAll variants applyRecipient contact email the invite was created for.
createdAtJSONRequired within parent
createdAt (allOf 1)stringAll variants applyFormat: yyyy-mm-ddThh:MM:ssZ
createdAt (allOf 2)JSONAll variants applyWhen the invite was created.
expiresAtJSONOptional
expiresAt (anyOf 1)JSONAlternative
expiresAt (anyOf 1) (allOf 1)stringAll variants applyFormat: yyyy-mm-ddThh:MM:ssZ
expiresAt (anyOf 1) (allOf 2)JSONAll variants applyWhen the invite expires, if it has an expiry.
expiresAt (anyOf 2)nullAlternative
idJSONRequired within parent
id (allOf 1)stringAll variants applyID for the invite
id (allOf 2)JSONAll variants applyThe invite's id, also embedded in 'onboardingUrl'.
namestringRequired within parentRecipient name the invite was created for.
notesJSONOptional
notes (anyOf 1)stringAlternativeNotes shown to the recipient, if any.
notes (anyOf 2)nullAlternative
onboardingUrlstringRequired within parentURL where the recipient submits their payment details.
paymentMethodsarrayRequired within parentPayment methods the recipient may submit details for.
Minimum items: 1
paymentMethods[]stringEach itemKnown values: ach, check, domesticWire, internationalWire, realTimePayment
recipientIdJSONOptional
recipientId (anyOf 1)JSONAlternative
recipientId (anyOf 1) (allOf 1)stringAll variants applyID for a Mercury account.
Format: uuid
recipientId (anyOf 1) (allOf 2)JSONAll variants applyThe existing recipient this invite is for, if any.
recipientId (anyOf 2)nullAlternative
requireTaxDocumentbooleanRequired within parentWhether the recipient must upload a tax document.
statusJSONRequired within parent
status (allOf 1)stringAll variants applyKnown values: created, completed, expired, declined
status (allOf 2)JSONAll variants applyStatus of the invite.

SDK function policy ID: mercury.listrecipientinvites. Catalog operation: mercury:listRecipientInvites. Rules can name either ID; function rules distinguish managed calls and conservatively cover raw calls sharing the route. Existing grant permissions and policy rules apply. wait() returns an immediate result or waits for a required approval; it never approves the request itself. Persist the approval ID to resume after a restart.

Provider errors retain their response; JSON decoding raises ProviderAPIError for provider failures. ManagedOperationError identifies contract/input/retention errors. See error handling and provider-specific behavior. Sensitive input may be refused before approval storage. A decoding error never resubmits a write.

Official provider source

Report an issue with this page

Necessary

Required for sign-in, security, authorization, and remembering your choices.

Always active

Analytics

Helps us understand which product and documentation features are useful.

Performance diagnostics

Uses performance tracing and privacy-masked session replay to diagnose problems.

You can change these choices at any time from Cookie settings.