Skip to content

Change contact stage

Contacts API · contacts.stage

URL · Fields · Example · Response · Try it

URL and authentication

POST https://YOUR-BACKEND/api/automation/v1/execute

Send Authorization: Bearer <connection key>, Accept: application/json and Content-Type: application/json. Create a connection.

This operation requires write access and CRM permission edit_contacts. The gateway invokes PATCH /api/v1/app/lead-contacts/{id}/stage internally. Use the POST URL above with your automation key, including for read and delete operations.

Request parameters

KeyTypeRequirement
operationstringRequired; exactly contacts.stage
parameters.idintegerRequired; positive record ID from your CRM
dataobjectRequired; see fields below
idempotency_keystringRequired; 8–100 characters. Unique per action; keep unchanged for identical retries.

Fields

Compatibility no-op: validates stageId but does not move the contact. To change the contact stage use contacts.update with contact_stage_id.

Fields below belong inside data. Dot paths describe nested objects; * means each array item. nullable permits null and sometimes validates a supplied field. in: lists allowed values; min: and max: limit the value, length or item count. exists: and exists_in_company: require a valid record ID. Conditional rules such as required_if and required_with refer to other fields in the same payload. Use YYYY-MM-DD for date-only values and timestamps with timezone offsets for follow-ups.

FieldTypeRequirementFormat / validation
stageIdintegerRequiredrequired; integer; exists_in_company:pipeline_stages

Example request

Replace the example IDs and values with records in your installation. Supply any additional custom fields required by your company.

{
  "operation": "contacts.stage",
  "parameters": {
    "id": 1
  },
  "data": {
    "stageId": 1
  },
  "idempotency_key": "example-event-12345"
}

Response

Returns a success acknowledgement, but this compatibility operation does not change the contact stage.

The gateway preserves the underlying HTTP status and JSON body. Successful requests return HTTP 200. A response may also include localized message fields.

Illustrative response excerpt (additional fields may be returned):

{
  "status": "success",
  "data": {
    "message": "Record saved successfully."
  }
}

Errors

HTTP statusMeaning
400A CRM business rule rejected the action.
401Missing, invalid, expired or revoked connection key.
403Connection access or CRM permissions do not allow this action.
404Operation or record unavailable.
409This idempotency key was already used with a different request.
413Request or result exceeds its size limit; reduce payload or page size.
422Missing or invalid fields, or a CRM business rule rejected the operation.
429Rate limit exceeded; wait before retrying.
500The server could not complete the operation.

Validation failures may return message / errors, or an error string with an optional fields array. The tester shows the actual HTTP status and full body. Read about limits and retries.

Try it

Brixit API v1

Try this request

contacts.stage

Requests run from your browser to your installation. Enter the backend URL shown in Brixit. Your connection key stays in this component’s memory and is cleared when you leave this page.

CRM permission: edit_contacts. Underlying route: PATCH /api/v1/app/lead-contacts/{id}/stage. Send this operation to POST /execute.

Example IDs are placeholders. Use your own record and lookup IDs. Required custom fields depend on your installation.

This is a compatibility no-op: it validates stageId but does not move the contact. Use contacts.update with contact_stage_id to change its contact stage.

POST /api/automation/v1/execute

Accept: application/json
Authorization: Bearer <connection key>
Content-Type: application/json

id must be a positive integer record ID.

Code uses a connection-key variable; your entered key is never included in copied examples.