Provider first requests

Public catalog snapshots observed 2026-10-28; first-request templates reviewed 2026-09-07.

• staging (https://api-staging.fictix.ai/api/v1/catalog/connector-capabilities, observed 2026-10-28): 60 catalog entries, 60 listed as available/preview, and 59 marked selectable; status histogram 59 available, 1 preview; fidelity histogram 60 approximate.
• production (https://api.fictix.ai/api/v1/catalog/connector-capabilities, observed 2026-10-28): 60 catalog entries, 60 listed as available/preview, and 59 marked selectable; status histogram 59 available, 1 preview; fidelity histogram 60 approximate. These status and fidelity values are public catalog reports. They do not show that each provider request succeeded, establish production request behavior, or promise strict upstream API parity. The request templates below were tested in staging only. Plan entitlements and company selection still apply.

FCI catalog status: staging: preview, not selectable; production: preview, not selectable. It uses execute and is not selectable in the standard connector picker. Check capability availability for your company before using its preview request.

Start with Connect your software for keys, SDK base URLs, scopes, and error handling. Read Provider workflows for supported writes, filters, pagination, and limits.

Download all first requests as JSON. The file contains public request templates and source release IDs; it contains no keys.

Request base and authentication

Append each table path to /api/v1/orgs/{slug}/ on your chosen API origin. Use https://api-staging.fictix.ai for staging and https://api.fictix.ai for production. Send the matching company or organization key as X-API-Key. Every first request needs read; FCI additionally needs execute.

For a GET, replace the path below with the one from the table:

curl --fail-with-body -sS \
  "$FICTIX_API_ORIGIN/api/v1/orgs/$FICTIX_PROJECT_SLUG/native/stripe/v1/customers" \
  -H "X-API-Key: $FICTIX_PROJECT_API_KEY"

POST read bodies and their content types are included below the table. These requests do not require a native-write idempotency key. Replace the two FCI body placeholders with the selected company project ID and a unique request ID.

Provider directory

Relay Financial is unavailable: a direct API contract has not been implemented. FCI uses execute. TriNet means HR Platform (formerly Zenefits); it does not describe TriNet PEO.

POST read bodies

The examples use the company-key variables from the connection guide. If you use an organization key, substitute $FICTIX_ORGANIZATION_API_KEY in the header.

Expensify request

Expensify: send application/x-www-form-urlencoded.

curl --fail-with-body -sS -X POST \
  "$FICTIX_API_ORIGIN/api/v1/orgs/$FICTIX_PROJECT_SLUG/native/expensify/Integration-Server/ExpensifyIntegrations" \
  -H "X-API-Key: $FICTIX_PROJECT_API_KEY" \
  -H "Content-Type: application/x-www-form-urlencoded" \
  --data-raw 'requestJobDescription=%7B%22type%22%3A%22get%22%2C%22inputSettings%22%3A%7B%22type%22%3A%22policyList%22%7D%7D'

Plaid request

Plaid: send application/json.

curl --fail-with-body -sS -X POST \
  "$FICTIX_API_ORIGIN/api/v1/orgs/$FICTIX_PROJECT_SLUG/native/plaid/transactions/get" \
  -H "X-API-Key: $FICTIX_PROJECT_API_KEY" \
  -H "Content-Type: application/json" \
  --data-raw '{}'

Sage Intacct request

Sage Intacct: send application/xml.

curl --fail-with-body -sS -X POST \
  "$FICTIX_API_ORIGIN/api/v1/orgs/$FICTIX_PROJECT_SLUG/native/sage_intacct/ia/xml/xmlgw.phtml" \
  -H "X-API-Key: $FICTIX_PROJECT_API_KEY" \
  -H "Content-Type: application/xml" \
  --data-raw '<request><control><senderid>fictix-sdk</senderid><controlid>first-read</controlid><uniqueid>true</uniqueid><dtdversion>3.0</dtdversion></control><operation transaction="true"><content><function controlid="first-read"><readByQuery><object>CUSTOMER</object><fields>*</fields><query/><pagesize>10</pagesize></readByQuery></function></content></operation></request>'

Dropbox request

Dropbox: send application/json.

curl --fail-with-body -sS -X POST \
  "$FICTIX_API_ORIGIN/api/v1/orgs/$FICTIX_PROJECT_SLUG/native/dropbox/2/files/list_folder" \
  -H "X-API-Key: $FICTIX_PROJECT_API_KEY" \
  -H "Content-Type: application/json" \
  --data-raw '{"path":""}'

FCI request

FCI: send application/json.

curl --fail-with-body -sS -X POST \
  "$FICTIX_API_ORIGIN/api/v1/orgs/$FICTIX_PROJECT_SLUG/execute" \
  -H "X-API-Key: $FICTIX_PROJECT_API_KEY" \
  -H "Content-Type: application/json" \
  --data-raw '{"org_id":"replace_with_company_project_id","user_id":"fictix-ui","turn_id":"replace_with_unique_request_id","capability_key":"fci.cash","args":{}}'

Adyen request

Adyen: send application/json.

curl --fail-with-body -sS -X POST \
  "$FICTIX_API_ORIGIN/api/v1/orgs/$FICTIX_PROJECT_SLUG/native/adyen/v72/paymentMethods" \
  -H "X-API-Key: $FICTIX_PROJECT_API_KEY" \
  -H "Content-Type: application/json" \
  --data-raw '{"merchantAccount":"FictixDemo"}'

Linear request

Linear: send application/json.

curl --fail-with-body -sS -X POST \
  "$FICTIX_API_ORIGIN/api/v1/orgs/$FICTIX_PROJECT_SLUG/native/linear/graphql" \
  -H "X-API-Key: $FICTIX_PROJECT_API_KEY" \
  -H "Content-Type: application/json" \
  --data-raw '{"query":"query { teams { nodes { id name } } }"}'

Monday request

Monday: send application/json.

curl --fail-with-body -sS -X POST \
  "$FICTIX_API_ORIGIN/api/v1/orgs/$FICTIX_PROJECT_SLUG/native/monday/v2" \
  -H "X-API-Key: $FICTIX_PROJECT_API_KEY" \
  -H "Content-Type: application/json" \
  --data-raw '{"query":"query { boards { id name } }"}'

Check application status

An HTTP 200 alone is insufficient for GraphQL, Sage Intacct, Expensify, and execute responses. Inspect GraphQL errors, XML operation statuses, Expensify responseCode, or execute status before using the returned data. See the connection guide for scope and error handling.