Cost CentersList cost centers

List cost centers

Use this endpoint to list all cost centers available for the authenticated company. The company context is automatically obtained from the access token.

The most common use is to retrieve the cost center id to classify transactions via PATCH /statements/v1/credit-card/{transactionId}.

Rules:

  • Returns all cost centers for the company, without pagination.
  • The responsible field is optional and deprecated — it will be removed in a future version. Do not use this field in new integrations.
curl -X GET "https://api-sandbox.contasimples.com/cost-centers/v1/cost-centers" \
  -H "Content-Type: application/json" \
  -H "Signature-Input: example_string" \
  -H "Signature: example_string" \
  -H "Authorization: Bearer YOUR_API_TOKEN"
{
  "items": [
    {
      "id": "fdafbfa7-5eeb-4d96-84aa-82b7c2e1b0ff",
      "companyId": "7c61b3f6-7353-46aa-80ef-3e27d95150ab",
      "name": "Marketing",
      "responsible": {
        "id": "76e2b52f-cf1d-415a-877b-57f51c4af228",
        "name": "João Silva"
      }
    },
    {
      "id": "b5829a71-38d2-4a5f-b73e-d5dd025336b0",
      "companyId": "7c61b3f6-7353-46aa-80ef-3e27d95150ab",
      "name": "Operações"
    }
  ]
}
GET
/cost-centers/v1/cost-centers
GET
Base URLstring

Target server for requests. Edit to use your own host.

Bearer Token
Bearer Tokenstring
Required

Bearer token from OAuth 2.0 client credentials. Format: Bearer TOKEN

Bearer token from OAuth 2.0 client credentials. Format: Bearer TOKEN
header
Signature-Inputstring

What was signed and the signature parameters, in the RFC 9421 format. A credential with a public key must send it on every call, reads included, or the request is refused with 401. The signature covers the @method, @path, and @query components, and also content-digest when there is a body. created and alg are required, and created is valid for 300 seconds. The full format, with examples, is in Request Signing.

header
Signaturestring

The signature of the base defined by RFC 9421, in base64, between : and under the same label used in Signature-Input, for example sig=:SGVsbG8gd29ybGQ=:. It always goes together with Signature-Input.

Request Preview
Response

Response will appear here after sending the request

Authentication

header
Authorizationstring
Required

Bearer token. Bearer token from OAuth 2.0 client credentials. Format: Bearer TOKEN

Headers

Signature-Inputstring

What was signed and the signature parameters, in the RFC 9421 format. A credential with a public key must send it on every call, reads included, or the request is refused with 401. The signature covers the @method, @path, and @query components, and also content-digest when there is a body. created and alg are required, and created is valid for 300 seconds. The full format, with examples, is in Request Signing.

Signaturestring

The signature of the base defined by RFC 9421, in base64, between : and under the same label used in Signature-Input, for example sig=:SGVsbG8gd29ybGQ=:. It always goes together with Signature-Input.

Responses

itemsarray
Required

Cost centers available for the company.