Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Remove the sandbox signing paragraph #132

Merged
merged 2 commits into from
Feb 13, 2020
Merged

Remove the sandbox signing paragraph #132

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
1b407ae
Merge tag '1.13.0.1' into develop
andrederoos Jan 30, 2020
d77893a
Update DESCRIPTION.md
lexym Feb 13, 2020
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
9 changes: 0 additions & 9 deletions DESCRIPTION.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -466,15 +466,6 @@ If you get an error telling you "The request signature is invalid", please check
- You use the data to sign to create a SHA256 hash signature.
- You have base64 encoded the SHA256 hash signature before adding it to the request under `X-Bunq-Client-Signature`.

## <span id="topic-signing-troubleshooting">Signing in sandbox</span>

You can choose to disable request signing on sandbox to simplify the testing. Here's how it works:

1. Set the `X-Bunq-Client-Signature` header of the request to `IGNORE_ONLY_FOR_TESTING`.
1. Send the request.

When ready to try your integration on production, remove the `IGNORE_ONLY_FOR_TESTING` header setting and implement signing in sandbox first. Make sure it works and then change the base URL to `https://api.bunq.com`.

# <span id="topic-headers">Headers</span>

HTTP headers allow your client and bunq to pass on additional information along with the request or response.
Expand Down