I cannot make my first request
Confirm the contract generation, server-only credential profile, entitlement, host, region, and required inputs.
Open launch journeyDeveloper support
Get from symptom to evidence fast.
Start with self-service diagnostics, then escalate with a credential-free packet that gives support enough context to act—without leaking tokens, personal data, or unrestricted telemetry.
Choose the symptom
Follow the shortest evidence path.
Each path starts with the exact artifact most likely to distinguish code, configuration, entitlement, provider, and state-machine failures.
An API call is failing
Use the exact endpoint contract, inspect typed status guidance, and compare a credential-safe cURL command without executing secrets in the browser.
Open API referenceMy SDK integration will not build
Select the exact platform playbook and repository guide; check version, package distribution, lifecycle ownership, and permissions.
Choose a platformA trip, task, or asset is stuck
Debug the state machine, not only the last HTTP response: current state, actor, version, idempotency, event time, outbox, and provider acknowledgement.
Inspect journey recoverySafe escalation packet
Send context, never credentials.
Copy the relevant facts into the authorized support channel. Redact tokens, keys, precise user location, personal data, raw payment information, and customer payloads.
Mappls product and exact operation or SDK repositoryAccount/application identifier and region—never the secretUTC timestamp and provider request/correlation IDHTTP status or typed SDK error with response body redactedExpected behavior, actual behavior, and minimal reproductionContract status, source fingerprint, SDK/runtime version, and last known good versionFor stateful systems: aggregate ID, current state/version, command ID, and last acknowledged eventBusiness impact, affected scope, retry safety, and the owner available for follow-up
Governed console request or official contact
Signed-in developers can use the support-request lifecycle for an application-scoped record. The Mappls terms page identifies contact@mappls.com as an official fallback. Your commercial agreement may name a more specific or time-sensitive route; use that when available.