Overview

Welcome to the Givebutter API! This documentation walks you through all of the currently available endpoints. We regularly update this documentation with new information.

The Givebutter API is organized around REST and provides a stateless interface for interacting with your Givebutter account. The Givebutter API supports JSON, and all requests return and require a valid JSON object.

Errors

The Givebutter API uses the standard HTTP status response codes:

Code

Description

400

Bad Request: The request could not be understood by the server due to malformed syntax.

401

Unauthorized: The request requires user authentication. The API access token may be missing or invalid.

403

Forbidden: The server understood the request, but is refusing to fulfill it. The API user does not have correct permissions.

404

Not Found: The resource requested does not exist or was not found.

405

Method Not Allowed: The method / verb specified in the request is not allowed for the resource.

500

Internal Server Error: The request was valid, but something failed on the server.