Fireberry icon

Fireberry

Consume Fireberry API

Actions14

Custom API Call

AI-generated

Overview

This node allows users to make custom API calls to the Fireberry API with flexible HTTP methods and parameters. It supports GET, POST, PUT, PATCH, and DELETE methods, enabling users to specify the endpoint path, query parameters, request body (in JSON or raw format), and custom headers. This is useful for scenarios where predefined operations do not cover specific API endpoints or when users need to interact with Fireberry's API in a customized way, such as fetching specific data, sending complex payloads, or integrating with unique API features.

Use Case Examples

  1. A user wants to retrieve data from a specific Fireberry API endpoint using a GET request with query parameters.
  2. A user needs to send a POST request with a JSON body to create a new record in Fireberry.
  3. A user wants to update a record using a PATCH request with raw body content and custom headers.

Properties

Name Meaning
HTTP Method The HTTP method to use for the API call (GET, POST, PUT, PATCH, DELETE).
Endpoint The API endpoint path to call, excluding the base URL. For example, /api/v2/record/account.
Query Parameters Key-value pairs to add as query parameters to the URL.
Send Body Whether to send a request body with the API call (applicable for POST, PUT, PATCH).
Body Content Type The content type of the request body, either JSON or raw text.
Body The JSON body content to send with the request (if Body Content Type is JSON).
Body (Raw) The raw body content to send with the request (if Body Content Type is raw).
Custom Headers Additional HTTP headers to include in the API request.

Output

JSON

  • json - The JSON response from the Fireberry API call.

Dependencies

  • Fireberry API authentication credential

Troubleshooting

  • Ensure the API endpoint path is correct and does not include the base URL.
  • Verify that the HTTP method matches the API endpoint's expected method.
  • If sending a body, ensure the body content matches the specified content type (JSON or raw).
  • Check that custom headers are correctly formatted and valid for the API.
  • Common errors include unsupported operations or invalid parameters, which will throw errors indicating the issue.

Discussion