RopelyStart with a supported check.
ropely.
Menu

Support

Find the next useful step.

Start with the source state and request ID. They tell us more than a screenshot of a generic error.

A check is inconclusive

Inspect coverage, freshness, source identity and rejected rows. Fix the missing evidence before interpreting a mismatch. Do not issue a second grant simply because the ledger cannot be joined.

An API request fails

401 means the credential needs attention; 403 means its scope does not permit the operation; 409 means an idempotency key was reused with different evidence. On 429, follow Retry-After. Save the X-Request-Id for support.

An integration is unavailable

Check the directory’s status and prerequisites. Paddle provider acceptance and some third-party client recipes are pending. A preview label is not a promise of a live production connection.

Contact support

Email support@ropely.io with a short explanation, UTC time and request ID. Never send keys or full exports. Support is asynchronous; no guaranteed response time or uptime SLA is included.

See the records behind a result.

Developer error reference · Contact details