Getting started

Every 73 Strings API sits behind one gateway. You need an account, an approved subscription to the right product, and that subscription's key.

1. Get a subscription key

1. Sign up with your work email and confirm the address.

2. Open Products and subscribe. 73 Monitor covers Asset Info, Captable, Dashboard-APIS, Documents, Financial Data, Financial-Data-V2 and Qualitative Data. Transaction Management covers Transaction API.

3. Subscriptions are approved by the 73 Strings team. Once approved, your primary and secondary keys are on your Profile.

2. Make your first call

Send the key in the subscription-key header. Request bodies are JSON. Responses are JSON too, except the Documents file download (file bytes) and Financial Data v2 (server-sent events).

The 73 Strings team shares your orgId and userId. Get entityIds from the Entity List operation in the Asset Info API.

curl -X POST "https://api-accord-eut-73strings.azure-api.net/financial-data/api/v1/ems/entityFinancialData" \

-H "subscription-key: YOUR_KEY" \

-H "Content-Type: application/json" \

-d '{"orgId": "YOUR_ORG_ID", "userId": "YOUR_USER_ID", "entityIds": ["YOUR_ENTITY_ID"], "companyName": "",

"attributeNames": ["Revenue*"], "versionName": "Actual", "versionId": "", "periodType": "Annual",

"currency": "USD", "units": "Millions", "asOfDate": "", "startDate": "2024-01-01", "endDate": "2024-12-31"}'

Every operation page has a Try this operation button that sends a real request with your key, so you can test without writing code.

Base URLs (EUT)

Asset Info https://api-accord-eut-73strings.azure-api.net/assetinfo

Captable https://api-accord-eut-73strings.azure-api.net/captable

Dashboard-APIS https://api-accord-eut-73strings.azure-api.net/dashboard

Documents https://api-accord-eut-73strings.azure-api.net/documents

Financial Data https://api-accord-eut-73strings.azure-api.net/financial-data

Financial-Data-V2 https://api-accord-eut-73strings.azure-api.net/financial

Qualitative Data https://api-accord-eut-73strings.azure-api.net/qualitative-data

Transaction API https://api-accord-eut-73strings.azure-api.net/transactions

Responses and errors

Check the body as well as the status. Some 200 responses carry "success": false with an errorCode, for example EXCE00021 when no data is found.

202 Accepted. Processing has not finished yet.

207 Partial success. Some items succeeded and some failed; the response lists each failure. Retry only the failed items.

400 The request failed validation. The body has message and errorCode.

401 The subscription key is missing or wrong, the subscription is not active, or the key belongs to a product that does not include this API. On the Transactions API, also check that orgId and userId belong to the key's user.

404 Either no operation matches the URL and method, or (Qualitative Data, Transactions API) a record you referenced was not found. Check the URL, the method and the IDs you sent.

422 Transactions API: every object in the request failed validation and nothing was saved. Fix the errors listed for each object and resend.

429 Too many requests. Wait, then retry with exponential backoff.

500 Server error. Retry read calls once. For Transactions writes, check whether the record was saved before you resend.

504 Gateway timeout. The processing state is unknown, so check the transaction before you resend.

Help

Email support@73strings.com with the endpoint, the request time and the response body.