How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Ubicquia Config API

The publicly described Ubicquia configuration and provisioning API ("Ubi Api", OpenAPI 3.0.0, 39 operations) covering sales orders, fulfillment details, device serial numbers and production files, distribution transformer and coil files, ICCID (cellular SIM) master records, customer lookup and user administration. Authenticated with an x-api-key header; the interactive Swagger UI at the same host redirects to a login, while the raw OpenAPI document is served publicly at /docs.

Ubicquia Config API is published by Ubicquia on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Configuration, Provisioning, Devices, Transformers, and Sales Orders. The published artifact set on APIs.io includes an OpenAPI specification.

This API exposes 39 operations across 39 paths, organized into 8 resource areas, and defines 14 schemas. It is described by OpenAPI 3.0.0, at version 0.0.1.

Requests are made against a single base URL, https://config.api.ubicquia.com/api/.

39 operations 39 paths 14 schemas 2 DELETE15 GET18 POST4 PUT

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.0.0
API Version
0.0.1
Base URL
https://config.api.ubicquia.com/api/
Authentication
API Key
License
Resource Areas
8

Authentication & Security 1

Ubicquia Config API declares 1 security scheme for authenticating requests. An API key is passed in the header as x-api-key (Api Key).

  • Api Key — Use header x-api-key: 'key' to send api key endpoints

Paths & Operations 39

Across 39 paths, the API surfaces 39 operations — 2 DELETE, 15 GET, 18 POST, 4 PUT. They span 8 resource areas: AuthCheck, Fulfillment Details, ICCID Master, Sales Order, Serial Number, Customer Detail, Transformer Details, User. Each is listed below with its method, path, parameters, and response codes.

AuthCheck 1

Operations about Auth Check

GET
/AuthCheck
Get all data
index → 401400404
Fulfillment Details 6

Operation about fulfillment details

POST
/fulfillment-detail
Add fulfillment Details
store body → 200400401404
POST
/delete-fulfillment-detail
Delete fulfillment Details
destroy body → 200400401404
POST
/fulfillment-detail-update
Upadate fulfillment Details
fulfillment-detail-update body → 200400401404
POST
/extended-fulfillment-detail
Extended fulfillment Details
extended-fulfillment-detail body → 200400401404
POST
/extended-fulfillment-detail-update
Extended fulfillment Details Update
extended-fulfillment-detail-update body → 200400401404
GET
/fulfillment-detail-status
get fulfillment detail status
1 param → 200400401404
ICCID Master 6

Operations about ICCID master

PUT
/iccid-master/update/{iccid}
Update ICCID master status
updateIccidRecord 1 param body → 200400401404422
POST
/update-iccid-master-file
Upload ICCID master CSV for bulk update
updateIccidMasterFile body → 200400401404422
POST
/delete-iccid-master-file
Upload ICCID master CSV for bulk delete
deleteIccidMasterFile body → 200400401404422
GET
/get-iccid-master-list
Get paginated ICCID master list
getIccidMasterList 6 params → 200400401404
GET
/log/iccid-master
Get latest ICCID master file upload status
getIccidMasterLatestLog → 200400401404
GET
/get-latest-failed-log/{type}
Download latest failed ICCID master CSV log
getIccidMasterFailedCsv 1 param → 200400401404422
Sales Order 6

Operations about Sales Order

PUT
/update-sales-order
Update Sales Order by id
update body → 200400401404
DELETE
/delete-sales-order
Deletes Sales order by id
destroy body → 200400401404
GET
/get-sales-order/{sales_order_number}
get sales order detail
1 param → 200400401404
POST
/add-sales-order
Add Sales Order by async
add-sales-order body → 200400401404
GET
/get-sales-order-status
get sales order status
2 params → 200400401404
POST
/add-sales-order-config
Add Sales Order on Config
add-sales-order-config body → 200400401404
Serial Number 5

Import serial Number details

POST
/update-production-file
Update Serial Number
update body → 200400401404
POST
/delete-production-file
Delete Serial Number
destroy body → 200400401404
GET
/get-serial-number-list
Get all serial number details
get-serial-number-list 6 params → 200400401404
GET
/check-uploaded-production-file-status
Get check uploaded production file status
check-uploaded-production-file-status → 200400401404
GET
/get-production-file-list
Get all production file details
get-production-file-list 9 params → 200400401404
Customer Detail 1

Get Customer Detail

POST
/get-customer-id
Get Customer Id
getcustid body → 200400401404
Transformer Details 8

Operation about transformer file upload

POST
/update-transformer-file
Update transformer details
update body → 200400401404
POST
/delete-transformer-file
Delete transformer details
destroy body → 200400401404
GET
/get-transformer-file-list
Get all transformer file list
get-transformer-file-list 8 params → 200400401404
GET
/check-uploaded-file-status
Get check uploaded file status
check-uploaded-file-status → 200400401404
GET
/get-transformer-file-by-id/{id}
Get transformer file by id
get-transformer-file-by-id 1 param → 200400401404
GET
/get-coil-file-by-id/{id}
Get transformer file by id
get-coil-file-by-id 1 param → 200400401404
POST
/update-coil-file
Update coil transformer details
update-coil body → 200400401404
POST
/delete-coil-file
Delete coil details
destroy-coil body → 200400401404
User 6

User

POST
/add-user
Add User
store body → 200400401404
PUT
/update-user/{id}
Update user id
update 1 param body → 200400401404
DELETE
/delete-user/{id}
Deletes User by id
destroy 1 param → 200400401404
GET
/get-user/{id}
get User By User Id
1 param → 200400401404
POST
/update-me
Update Me
update me body → 200400401404
PUT
/changeUserCustomerStatus/{id}
change User Customer Status
changeUserCustomerStatus 1 param body → 200400401404

Schemas 14

The contract defines 14 schemas that model the data the API accepts and returns. The most detailed are User (16 properties), ApiRequestLog (6 properties), SalesOrder (5 properties), SerialNumberDetail (4 properties). Each schema is shown below with its type and property counts.

ApiRequestLog
object
6 properties
Country
object
Country Model
FactoryConfigs
object
FulfillmentDetails
object
4 properties
FulfillmentJobDetails
object
4 properties
FulfillmentLogs
object
4 properties
PasswordHistory
object
ProductionFileUploads
object
ReportLog
object
SalesOrder
object
5 properties
SerialNumberDetail
object
4 properties
TransformerDetail
object
4 properties
TransformerFileUpload
object
User
object
User
16 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

ubicquia-config-api-openapi-original.json Raw ↑
Where this information came from

This is an independent, third-party profile of Ubicquia Config API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.