Libraries tagged by ApiAdmin

aiadmin/core

0 Favers
4 Downloads

ai admin core package

Go to Download


kphcdr/axeadmin-laravel

50 Favers
118 Downloads

axeadmin-laravel

Go to Download


smallruraldog/amis-admin

110 Favers
672 Downloads

amis admin

Go to Download


codecoz/aim-admin

21 Favers
35 Downloads

Welcome to AimAdmin, the ultimate Laravel admin panel plugin engineered to elevate developers' productivity and streamline development workflows.

Go to Download


suqflash/piadmin

0 Favers
15 Downloads

Webman plugin suqflash/piadmin

Go to Download


popo1h/aadmin-core

0 Favers
40 Downloads

core for aadmin

Go to Download


oneko/apcuadmin-bundle

0 Favers
211 Downloads

APCu administration

Go to Download


noistudio/artadmin-mongodb

0 Favers
5 Downloads

Админ панель для laravel ( Mongodb версия)

Go to Download


noistudio/artadmin

2 Favers
142 Downloads

Админ панель для laravel

Go to Download


kfteam1991/amis-admin

0 Favers
8 Downloads

amis admin

Go to Download


joacub/at-admin

0 Favers
236 Downloads

The missing ZF2 Admin module constructor.

Go to Download


aliamini78/module-builder

2 Favers
8 Downloads

Package for making modules in Laravel.

Go to Download


kruegge82/jumingo

0 Favers
31 Downloads

## About With the JUMINGO shipping API you can import your shipments into your JUMINGO account from any source. The functionalities of the API include creating and updating shipment drafts, fetching suitable shipment rates for a given shipment and purchasing shipping labels. Furthermore, you can retrieve tracking data and fetch shipping labels and documents for all your purchased shipments. The current main purpose of the API is to connect your account to e-commerce systems and marketplaces. ## General The API is organized around REST. Our API has resource-oriented URLs and uses HTTP response codes to indicate API errors. We use built-in HTTP features, like HTTP authentication and HTTP verbs. All API requests must be made over HTTPS. Calls made over plain HTTP will return errors. Request data is passed to the API as JSON objects and JSON is also returned by all API responses, including errors, although our API SDKs convert requests and responses to appropriate language-specific objects. Best practice usage of the API and business logic is described in the supplementary [integration guide](https://www.jumingo.com/cms/JUMiNGO_API-integration-guide.pdf "JUMiNGO API Integration Guide"). ## Base URL The base URL for all calls is: `https://api.jumingo.com/v1` ## HTTP status codes HTTP response codes in the `2xx` range indicate success. Codes in the `4xx` range indicate an error on the client side (e.g. a required parameter is missing). Codes in the `5xx` range indicate an error with our servers. Each error should provide an error code and an error message with further information. HTTP status code | Description ---------------- | ----------- 200, 201, 204 - OK | Everything worked. 400 - Bad Request | The request was unacceptable, often due to missing a required parameter or a validation error. 401 - Unauthorized | No valid API key has been provided or your account is disabled. 403 - Forbidden | You are not allowed to talk to this endpoint. This can either be due to a wrong authentication or when you’re trying to reach an endpoint that your account isn’t allowed to access. 404 - Not Found | The requested resource doesn’t exist. 500, 502, 503, 504 - Server Errors | Something went wrong on our side. Please contact our support if you receive this error. ## Authentication All API requests requires authentication. Unauthorized calls will return errors. Authenticate by including your API key in the `X-AUTH-TOKEN` HTTP header of each API call, e.g.: `X-AUTH-TOKEN: INSERT_YOUR_API_KEY` You can find your API key in your JUMINGO user account. You can get access to the JUMiNGO customer API by enabling it in your [user account](https://www.jumingo.com/de-de/users/connections/create/8). After activation, you will get your personal API key. ## Date/Time Format All values of type `string ` are defined in a specific [RFC 3339](https://tools.ietf.org/html/rfc3339#section-5.6) format and must also be formatted accordingly for requests. The format is: YYYY-MM-DD hh:mm:ss Example: 2018-07-26 15:54:13 All dates and times are specified in UTC (Coordinated Universal Time).

Go to Download


ircsasw/yii2-ace-timeline-widget

1 Favers
252 Downloads

Timeline Widget for ACEAdmin theme.

Go to Download


saithink/saiadmin

283 Favers
11879 Downloads

webman plugin

Go to Download


<< Previous Next >>