githubEdit

Test Credentials

You can test your integration using Ventrata's EdinExplore, a fictional supplier account created for testing and demonstration.

This account includes common product configurations and gives you access to products, bookings, and Ventrata API logs.

Obtaining Test Credentials

Register for test credentials here:

https://dashboard.ventrata.com/octo/signuparrow-up-right

The signup form asks for your company name, email, and password. You will use these credentials to access the Booking Portal, where you can review bookings, check availability, and view logs.

After creating your account, you will see a screen similar to this:

Account setup screen with endpoint and key

The API endpoint and key shown on that page can be used to test your integration with EdinExplore.

Booking Portal

Use your new credentials to sign in to the EdinExplore agent portal:

https://edinexplore.portal.ventrata.site/arrow-up-right

It will look like this:

![EdinExplore agent portal](../.gitbook/assets/CleanShot 2023-06-02 at [email protected])

On the Bookings tab, you can view all bookings made through the reseller portal and API. This helps verify field values and confirm that requests are being recorded correctly.

Sample of a booking in the agent portal

API Logs

In addition to the booking portal, the API Logs tab lists all API requests received for your credentials.

Selecting a request opens a request/response view.

Live Testing

If you need to test with live supplier credentials, use the Octo-Env: test request header.

This header marks bookings made with live credentials as test sales in Ventrata. Test sales do not consume availability, barcodes do not redeem, and they are not invoiced. Use Octo-Env: test for test bookings and Octo-Env: live to disable test mode and sell live.

Suppliers can force your connection into test mode, which processes all requests as Octo-Env: test. This is commonly used when suppliers want to review test bookings before approving go-live.

Last updated