SuppliersUpdate Supplier

Update Supplier

Updates the name of an existing supplier.

Rules:

  • The name field is required and cannot be empty.
  • You cannot update to a name already used by another supplier in the same company.

Use this endpoint to fix typos or update a supplier's legal name.

curl -X PUT "https://api-sandbox.contasimples.com/suppliers/v1/suppliers/16" \
  -H "Content-Type: application/json" \
  -H "Signature-Input: example_string" \
  -H "Signature: example_string" \
  -H "Content-Digest: example_string" \
  -H "Authorization: Bearer YOUR_API_TOKEN" \
  -d '{
  "name": "Updated Supplier LLC"
}'
{
  "id": 16,
  "name": "Updated Supplier LLC",
  "type": {
    "id": 1,
    "type": "CUSTOM"
  }
}
PUT
/suppliers/v1/suppliers/{id}
PUT
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
path
idinteger
Required

Numeric supplier identifier — use the id field returned by GET /suppliers/v1/suppliers.

Format: int32
Content-Typestring
Required

The media type of the request body

Options: application/json
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.

header
Content-Digeststring

Hash of the request body in the RFC 9530 format, with sha-256 or sha-512, for example sha-256=:X48E9qOokqqrvdts8nOJRJN3OWDUoyWxBf7kbu9DBPE=:. It is required when the request has a body and the credential has a public key, and in that case Signature-Input must include the content-digest component.

namestring
Required

New supplier name. Must be unique among your registered suppliers.

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

Path Parameters

idinteger
Required

Numeric supplier identifier — use the id field returned by GET /suppliers/v1/suppliers.

Example:
16

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.

Content-Digeststring

Hash of the request body in the RFC 9530 format, with sha-256 or sha-512, for example sha-256=:X48E9qOokqqrvdts8nOJRJN3OWDUoyWxBf7kbu9DBPE=:. It is required when the request has a body and the credential has a public key, and in that case Signature-Input must include the content-digest component.

Body

application/json
namestring
Required

New supplier name. Must be unique among your registered suppliers.

Example:
Updated Supplier LLC

Responses

idinteger
Required

Numeric supplier identifier.

companyIdstring

Always returns the ID of the authenticated company.

namestring
Required

Supplier name.

typestring
Required

Supplier type. Indicates whether created by your company (CUSTOM) or platform-seeded (DEFAULT).