Lightroom Services API: generic openresty 403 on /v2/account and /v2/health from our server only - is our IP blocked?

Question

We are building an integration with the Lightroom Partner API (Lightroom Services on an OAuth Web App credential; the project is in "In Development" status with beta users added).

Symptom: from our production server (hosted at Hetzner) authenticated calls are refused with a generic HTML page. GET https://lr.adobe.io/v2/account with our X-API-Key and a valid user access token returns HTTP 403, Server: adobe, Content-Type: text/html, and the body is the generic "403 Forbidden ... openresty" page.

What we verified:

- The IMS authorization-code exchange succeeds and the token is valid: issued for our client, scopes openid, AdobeID, lr_partner_apis, lr_partner_rendition_apis, offline_access.

- An invalid token gets a normal JSON error (HTTP 401, code 4002), so the gateway validates tokens before it refuses us.

- GET /v2/health with only our API key returns 200 from a regular home internet connection, but 403 from our server.

- Same result with two different Adobe accounts (the project owner and a second beta user who has a Lightroom subscription), so it does not look like an account or entitlement problem.

- Developer Console: Lightroom Services attached, OAuth Web App credential connected, beta users saved, redirect URI and pattern correct.

This looks like the case in this thread from September, whose author concluded that their IP address was blacklisted by Adobe: https://community.adobe.com/questions-680/lightroom-api-access-1643014

X-Request-Id values from failed calls (Oct 22, 2026): b08862b7-71c7-4be9-bfd3-a131d21fa83e, 2807784a-08a4-4312-8d7c-ea7d42f2a7a1, 038aa2b2-cc09-43c8-96d2-5d023c333bcb. Adobe can find our project, API key and source IP from these IDs; I would rather not post those publicly, and I am happy to share them privately.

Questions:

1. Is our server's IP (or the Hetzner network) blocked on lr.adobe.io, and how can it be unblocked or allowlisted?

2. If it is not an IP block: is there an extra enablement or approval step for Lightroom Services partner access that beta users in development mode also need?

Thank you!

Tranquil_code6992 · Answer

Update with a cleaner test, in case it helps narrow this down.

From our server's own shell, with plain curl (no PHP, no containers, nothing custom), GET https://lr.adobe.io/v2/health with only our API key returns HTTP 403, Server: adobe, Content-Type: text/html (the generic "403 Forbidden" page). The same API key returns 200 with the version JSON from other networks, including when called through the same HTTP client library our application uses. A made-up API key sent from the same server gets Adobe's normal JSON error.

So the gateway accepts connections from our server and recognizes our key as valid, but only from that source address it answers with the generic 403 page. Request ID of the latest failing call: 3ca2f628-78e1-4450-b9ec-b2f7f4deca46 (Oct 25, 2026, 15:10 GMT).

This looks like an IP- or network-based restriction applied to our API key. Could someone from Adobe check the request IDs in this thread and tell us whether our server address is blocked, and how to get it allowlisted? Happy to share the project details and the IP privately.

Sign up

To post, reply, or follow discussions, please sign in with your Adobe ID.

Sign in to Adobe Community

To post, reply, or follow discussions, please sign in with your Adobe ID.