ifood.connection.complete-authorization

Exchange a merchant's authorization code for a durable iFood grant

Exchange the merchant's authorization code for a durable grant.

Leg two, and not a poll. iFood shows the authorization code to the merchant in the Portal after they confirm the user code, and the merchant hands it back — the provider expects authorization_code supplied and has no method that retrieves it. There is nothing to wait for, so there is no schedule_transition here.

The exchange happens by writing the code beside the verifier already on the connection and then opening a provider: the service builds credentials from the connection, and connect performs the authorization_code grant. Doing it that way means this workflow never handles a token itself.

Afterwards the single-use material is deleted in the same write that stores the refresh token. An authorization code survives its exchange only as a stale bearer credential in an encrypted blob nobody audits.

Overview

Property	Value
Workflow type	Linear
Library	App-ifood
Version	1.0

Input Schema

Field	Type	Required	Default	Description
organization_uuid	string	Yes	—	—
connection_uuid	string	Yes	—	The merchant connection begun by ifood.connection.begin-authorization
authorization_code	string	Yes	—	The code iFood showed the merchant after they confirmed the user code
workflow_run_id	string	No	—	—

Output Schema

Field	Type	Required	Default	Description
organization_uuid	string	Yes	—	—
connection_uuid	string	Yes	—	—
workflow_run_id	string	No	—	—
authorized	boolean	Yes	—	—
merchants_granted	integer	Yes	—	—
merchant_refs	list	Yes	—	—
completed_at	string	Yes	—	—
failure_reason	string	No	—	—
failure_type	string	No	—	—
failed_action	string	No	—	—
failed_step	json	No	—	—
failed_layer	integer	No	—	—
failed_at_state	string	No	—	—
error	string	No	—	—
error_type	string	No	—	—
failed_at	string	No	—	—
provider_request_ref	string	No	—	—
retryable	boolean	No	—	—

States

State	Initial	Terminal	Success	Auto-advance	Description
initiated	Yes	No	—	execute	—
executing	No	No	—	complete	—
completed	No	Yes	Yes	—	—
failed	No	Yes	No	—	—

State Diagram

Transitions

From	Action	To	Description
initiated	execute	executing	—
executing	complete	completed	—
* (any state)	fail	failed	—

Outcomes

Outcome	Type	Description	State Data Keys
authorized	SUCCESS	The merchant's authorization was exchanged for a durable grant	authorized, merchants_granted, merchant_refs
failed	FAILURE	The authorization exchange failed	failure_reason, failure_type, retryable

Business Errors

Code	Message Template
IFOOD_ORGANIZATION_CONTEXT_INVALID	Authenticated organization context is missing or does not match the workflow input
IFOOD_CONNECTION_NOT_FOUND	iFood connection {connection_uuid} was not found in the authenticated organization
IFOOD_CONNECTION_WRONG_PROVIDER	Connection {connection_uuid} is not an iFood connection
IFOOD_CONNECTION_SERVICE_UNAVAILABLE	The shared cloud connection service is unavailable
IFOOD_PROVIDER_CAPABILITY_MISSING	The installed iFood provider does not expose the required API operation
IFOOD_AUTHENTICATION_FAILED	iFood rejected the connection credentials or bearer token
IFOOD_PROVIDER_REQUEST_FAILED	The iFood API request failed
IFOOD_RESPONSE_SHAPE_INVALID	The iFood Merchant API returned an invalid merchant record
IFOOD_PAGINATION_INVALID	Merchant page must be at least 1 and limit must be between 1 and 100
IFOOD_SALES_WINDOW_INVALID	Sales dates must use YYYY-MM-DD, be ordered, and span no more than 8 inclusive days
IFOOD_SALES_PAGINATION_INVALID	Sales page must be a zero-based integer
IFOOD_SALES_RESPONSE_SHAPE_INVALID	The iFood Financial Sales API returned an invalid response
IFOOD_FINANCIAL_EVENTS_WINDOW_INVALID	Financial Events dates must use YYYY-MM-DD, be ordered, and span no more than 33 inclusive days
IFOOD_SETTLEMENTS_WINDOW_INVALID	Settlements dates must use YYYY-MM-DD, be ordered, and span no more than 90 inclusive days
IFOOD_FINANCIAL_PAGINATION_INVALID	Financial page must be one-based and page_size must be between 100 and 300
IFOOD_FINANCIAL_EVENTS_RESPONSE_SHAPE_INVALID	The iFood Financial Events API returned an invalid response
IFOOD_SETTLEMENTS_RESPONSE_SHAPE_INVALID	The iFood Settlements API returned an invalid response
IFOOD_DATA_ENVIRONMENT_INVALID	data_environment must be exactly 'production' or 'homologation'
IFOOD_DATA_ENVIRONMENT_UNSUPPORTED	The installed iFood provider does not support data_environment; upgrade ltinteg-cloud-connections to request homologation records

API Usage

POST /api/workflows/start
Content-Type: application/json

{
  "workflow_type": "ifood.connection.complete-authorization",
  "initial_data": {
    "organization_uuid": "value",
    "connection_uuid": "value",
    "authorization_code": "value"
  }
}