LogoLogo
  • Introduction
  • OVERVIEW
    • About ParqEx
      • -- Marketplace
      • -- Access+
      • -- GuestParq & GuestAccess
      • -- Enforcer
    • API Requirements
    • Roles and Permissions
  • GETTING STARTED
    • Requesting an Account
    • Using RESTful Tools
    • Webhooks
  • Embedding ParqEx in Native Mobile Apps
    • Overview
    • FAQ
    • Technical Documentation
      • iOS Implementation Guide
      • Android Implementation Guide
  • THE BASICS
    • Entities
    • Best Practices
    • Testing Accounts
  • OAUTH
    • Overview
    • How to Authorize Access
      • Step 1: Generate Authorization URL
      • Step 2: Handle Authorization Response
      • Step 3: Request an Access Token
      • Step 4: Call API Endpoints
      • Step 5: Refresh the Tokens
  • API ENDPOINTS
    • Overview
    • Get User Info
    • Get User Settings
    • Get User Devices
    • Toggle Access Point
    • Invite User (internal)
    • Get Access History
Powered by GitBook
On this page

Was this helpful?

  1. GETTING STARTED

Using RESTful Tools

PreviousRequesting an AccountNextWebhooks

Last updated 4 years ago

Was this helpful?

We love tools. Many of them make prototyping against APIs quick and easy. However, there are limitations to these tools that you must be aware of which will cause errors messages when contacting the Garageio API.

​ - Echo is a great little native app for OSX for testing APIs but it is known to block/override a couple of critical headers required by the Garageio Service, such as Accept-Charset.

​ - Postman is a fairly feature-rich app that runs atop the Google Chrome web browser. It too restricts a ton of headers, which are conveniently listed in Postman’s documentation. Some headers Postman blocks will certainly cause an issue with testing the Garageio Service:

  • Accept-Charset

  • Accept-Encoding

  • Host

Echo
POSTMAN