Marketo API mock: lead sync and daily quota 607

Sync Lead

POST /rest/v1/leads.json

Simulates creating, updating or upserting lead records through the Sync Leads API. The request action and lookupField describe how matching records are handled; the selected behaviour determines the returned envelope and per-record results.

Request content type: application/json

Request example

{
  "action": "createOrUpdate",
  "lookupField": "email",
  "input": [
    {
      "email": "alex@example.test",
      "firstName": "Alex",
      "lastName": "Example"
    }
  ]
}

Available behaviours (12)

• Lead synced

  Documented

  Sync Leads creates or updates records through one endpoint and returns per-record status results.

  HTTP 200

  Verify that your client handles a successful response.

  • HTTP 200 with the Marketo requestId, success and result envelope.

• Existing lead updated

  Documented

  Selected updateOnly success; the receiver does not store or look up leads.

  HTTP 200

  Verify that your client handles a successful response.

• Mixed record results

  Documented

  HTTP 200 and success true can contain both an updated lead and a skipped input record, in input order.

  HTTP 200 · 1002

  Verify that your client understands this provider-specific outcome.

• Invalid or expired access token

  Documented

  A rejected access token is a response-level 602 error; Marketo returns it inside the API response envelope.

  HTTP 200 · 602

  Test credential refresh and authentication recovery.

  • Clients refresh the token after 601 or 602; this mock does not perform token exchange.

• Required lead lookup value missing

  Documented

  A Sync Lead input record without its selected email lookup value is skipped with record-level error 1002.

  HTTP 200 · 1002

  Test field mapping and useful validation feedback.

  • The failed lead is represented in result[].reasons while the top-level request remains successful.

• Lead validation failed

  Documented

  A record with an unsupported field is skipped with a record-level 1006 reason while the request envelope remains successful.

  HTTP 200 · 1006

  Test field mapping and useful validation feedback.

  • Record-level errors appear under result[].reasons and do not set top-level success to false.

• Lead not found

  Documented

  The updateOnly action skips a record when its lookup key does not match an existing lead (1004).

  HTTP 200 · 1004

  Check how your client handles a missing record or resource.

• Lead already exists

  Documented

  The createOnly action skips a record whose lookup key already exists (1005).

  HTTP 200 · 1005

  Exercise conflict handling before repeating a write.

• REST rate limit exceeded

  Documented

  Marketo reports its shared 100-calls-per-20-seconds limit as response-level error 606.

  HTTP 200 · 606

  Verify bounded backoff and retry handling.

  • Use exponential backoff; Marketo does not define an HTTP Retry-After header for this response.

• Daily API quota reached

  Documented

  Marketo reports exhausted daily subscription allocation as response-level error 607.

  HTTP 200 · 607

  Check that persistent allocation or billing limits do not cause endless retries.

  • This daily allocation limit is distinct from short-term rate limiting.

• API temporarily unavailable

  Documented

  Marketo reports temporary REST API unavailability as response-level error 608.

  HTTP 200 · 608

  Test recovery and error reporting during simulated service failures.

• Delayed sync response

  Synthetic

  Synthetic delay for client deadline and retry testing.

  HTTP 200 · 250 ms delay

  Exercise client deadlines and timeout recovery.

  • Artificial delay only; the Marketo response remains a normal success envelope.