Skip to content

InvalidRequestException when submitting a request that contains unescaped characters #17

@rp-julienguery

Description

@rp-julienguery

We have noticed in our use of your API that when a Transaction object contains information with unescaped characters - like á for example - your service can't decode the JSON and an InvalidRequestException exception is thrown by the API with the message There was a problem decoding the request body as a JSON object.

Should your API escape the characters before sending a request?
If not, at least specify in the doc how the strings should be escaped/encoded.

Thanks!

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions