The e-guma Developer Hub

Welcome to the e-guma developer hub. You'll find comprehensive guides and documentation to help you start working with e-guma as quickly as possible, as well as support if you get stuck. Let's jump right in!

Get Started    

Overview

Integration in your system

For a smooth integration process we provide an Integration Guide with information for the different use cases. Before you start the development we like to have a call with you to discuss the integration process. Please contact us to schedule a call: [email protected]

REST

The e-guma API is organized around REST. Our API is designed to have predictable, resource-oriented URLs and to use HTTP response codes to indicate API errors.

Always set the required headers

As we only support JSON data, the API expects the Content-Type header to be set to application/json.

Response format

JSON will be returned in all responses from the API.

Authentication

You authenticate to the e-guma API by providing an API key in the request. The API keys are assigned to e-guma users. You can manage the API keys from the e-guma account. There can be multiple API keys active at one time. Authentication to the API occurs via query string in the request URL. You must set the API key for all requests.

Error handling

Errors are returned using standard HTTP error code syntax. An additional message is included in the body of the return call as plain text.

400

Bad Request - Often missing a required parameter.

401

Unauthorized - No valid API key provided.

500

Server errors - something went wrong on e-guma's end.

Questions

For questions, please write to [email protected].

Updated 21 days ago

Overview


Suggested Edits are limited on API Reference Pages

You can only suggest edits to Markdown body content, but not to the API spec.