Request method
The core methods supported by the API include GET , POST , PUT , PATCH and DELETE , each method has a different purpose:
GET : Retrieve data from the server. They are typically used to obtain lists of projects, tests , reports, etc.
POST : , such as a project, folder, or italy business email list manual test. It requires API write access .
PUT : Completely update an existing resource, such as modifying project or folder details. Requires API write access.
PATCH : Partial update resource, allowing changes to specific fields. For example, you can enable/disable automated tests, move tests between folders, or add custom annotations to tests. Requires API write access.
DELETE : Delete an entity such as a project, folder or test report. Requires API write access.
access rights
Access to API methods depends on user permissions:
GET is available on the Enterprise plan (API access).
POST and other write operations require Company Plan (API Write Access).
Free accounts do not have API access.
API key
Interacting with the API requires an API key, which can be found in your account settings. It must be included in the request header:
x-api-key: <your_api_key>
Request format
All requests must be sent via HTTPS , and data is transmitted in JSON format.
If you follow these guidelines, you can effectively leverage the GlockApps v2 API to perform a variety of email delivery and automation tasks.
Methods for making API requests
There are multiple ways to perform requests to the GlockApps v2 API, including Swagger UI , cURL , Postman , and other tools:
Swaggering user interface
Interactive tools integrated into files that allow you to send requests and view results directly from the browser, without coding.
curly
A command-line utility for making HTTP requests, ideal for use in scripting and terminal environments.
postman
A popular API testing tool that allows you to send requests, set parameters and analyze responses.
