Solved

Jwt payload is an invalid JSON

Forum|Forum|3 months ago
August 5, 2025
2 replies
91 views

G

+2

ganesh.stha
New Voice

Hi all,

I’m using a JWT Grant flow in PHP (RS256).
The token works perfectly against the sandbox endpoint:

https://demo.docusign.net/restapi/v2.1/accounts

But when I send the exact same JWT to the Maestro (developer) endpoint:

https://api-d.docusign.com/v1/accounts

DocuSign returns:

“Jwt payload is an invalid JSON”

Does anyone know why the payload is accepted in demo but rejected in Maestro/API-D?

What’s different ?

Thanks in advance for any help 🙏

Best answer by Achille.Nisengwe

Hi @ganesh.stha ,

There is a small difference when authenticating with the Docusign Maestro API and the eSignature API. When requesting the access token in your OAuth2 JWT flow to use with the Docusign Maestro API, you must request the signature scope and a special Docusign Maestro scope called aow_manage.

Please consult the link below to learn more about the supported Maestro API endpoints.

https://developers.docusign.com/docs/maestro-api/reference/

A

+4

Achille.Nisengwe
Docusign Employee
Answer
Forum|Forum|3 months ago
August 6, 2025

Hi @ganesh.stha ,

There is a small difference when authenticating with the Docusign Maestro API and the eSignature API. When requesting the access token in your OAuth2 JWT flow to use with the Docusign Maestro API, you must request the signature scope and a special Docusign Maestro scope called aow_manage.

Please consult the link below to learn more about the supported Maestro API endpoints.

https://developers.docusign.com/docs/maestro-api/reference/