cURL
curl --request POST \
--url https://api.slash.com/contact \
--header 'Content-Type: application/json' \
--header 'X-API-Key: <api-key>' \
--data '
{
"name": "<string>",
"recipientLegalName": "<string>",
"recipientEmail": "<string>"
}
'{
"contact": {
"id": "<string>",
"name": "<string>",
"recipientLegalName": "<string>",
"recipientEmail": "<string>",
"address": {},
"data": {},
"archivedAt": "2023-11-07T05:31:56Z"
}
}Contact
Create contact
Create a new contact for your legal entity. Contacts are used as invoice recipients.
POST
/
contact
cURL
curl --request POST \
--url https://api.slash.com/contact \
--header 'Content-Type: application/json' \
--header 'X-API-Key: <api-key>' \
--data '
{
"name": "<string>",
"recipientLegalName": "<string>",
"recipientEmail": "<string>"
}
'{
"contact": {
"id": "<string>",
"name": "<string>",
"recipientLegalName": "<string>",
"recipientEmail": "<string>",
"address": {},
"data": {},
"archivedAt": "2023-11-07T05:31:56Z"
}
}Documentation Index
Fetch the complete documentation index at: https://docs.slash.com/llms.txt
Use this file to discover all available pages before exploring further.
Authorizations
api_keybearer
API key authentication for public API requests.
Keys come in two flavors:
- Legal-entity-scoped keys are pinned to a single legal entity. Minted via the dashboard under a specific entity; every request acts on that entity.
- User-scoped keys are pinned to a user and span every legal
entity that user has access to. Every request made with a
user-scoped key (except
GET /legal-entity, which lists the legal entities the user can access) must include anx-legal-entityheader naming the legal entity the request is operating on. Requests without the header are rejected with400. The authenticated user must have an active permission role on the supplied legal entity, otherwise the request is rejected with403.
Query Parameters
The legal entity ID. Required if authenticating with access to multiple legal entities.
Body
application/json
Display name of the contact.
The relationship type of the contact.
Available options:
contact, vendor Legal name of the recipient.
Email address of the recipient.
Show child attributes
Show child attributes
Response
OK
A contact represents a counterparty (customer, vendor, etc.) associated with a legal entity.
Show child attributes
Show child attributes
⌘I