API Client Migration: From Postman to Bruno
Why We Switched to the Offline-Focused Bruno Every API developer knows that to build an API properly you need a reliable client for testing and interacting with the API. Ideally this tool should be free, it should store endpoint collections and share them easily with your team, and it should be fast and secure.
Content Negotiation in Dotkernel REST API
Content negotiation is an important aspect of RESTful APIs to make it possible for diverse systems to work seamlessly together. It's based on enabling clients and servers to agree on the format and language of data they exchange.
Error reporting endpoint in Dotkernel API
Dotkernel API has received a lot of love from our developers, with regular updates to the platform for years. We use Dotkernel API in our projects, so any bugs and issues are addressed as soon as they are found.
OpenAPI implementation in Dotkernel API
What is OpenAPI? The OpenAPI Specification provides a consistent way to develop and interact with an API. It defines API structure and syntax in a universal way, regardless of the programming language used in the API's development.
DotKernel API versus Laminas API Tools
Below we have created an analysis of the basic features available in Laminas Api Tools and DotKernel API. It's intended to highlight the differences between the two and also to showcase why DotKernel API is a good alternative for Laminas API Tools, especially considering the latter's archived status.
API Endpoint to Collect Client Errors
API Endpoint to Collect Client Errors Let's say you have a (Client) Frontend (e.g.
How to implement MailChimp in DotKernel API
This article will walk you through the process of implementing MailChimp into your instance of DotKernel API using drewm/mailchimp-api Step 1: Add the library to your application using the following command: composer require drewm/mailchimp-api Step 2: Create configuration file config/autoload/mailchimp.global.
DotKernel API 1.0.0 Released
Dotkernel API has come a long way since this post was created. Check out the newest version of Dotkernel API to stay up to date with the latest functional and security features.
DotKernel API Server Side Authorization
This article covers the basic authorization of a Server Side application built using DotKernel API Protecting an endpoint no-auth: the resource can be accessed without the need of authentication/authorization authentication: the resource can be accessed only by authenticated users authorization: the resource can be accessed only by authenticated AND authorized users Configuring access to the endpoints is done by editing the following config file: config/autoload/authorization.local.
DotKernel API Client Side Authorization
This article covers the basic authorization of a Client application which use a backend built using DotKernel API Authorization Request Client application users send a POST request to the backend containing the following JSON object: { "grant_type": "password", "client_id": "{API_CLIENT}", "client_secret": "{API_CLIENT_SECRET}", "scope": "{SCOPE}", "username": "{USERNAME/EMAIL}", "password": "{PASSWORD}" } Authorization Response If the credentials are correct, the API will return a JSON object containing the authentication data: { "token_type": "Bearer", "expires_in": 86400, "access_token": "..