DataConnect API Guide

REST API Reference

Base URL: https://dataconnect.genrocket.com

The flow is: 

(1) POST /daas/login → get a JWT, then 

(2) POST /daas/generate with that JWT. Two discovery endpoints ( /daas/industries , /daas/generators ) need no token.

Authenticate — POST /daas/login

HTTP Request

POST /daas/login HTTP/1.1
Host: dataconnect.genrocket.com
Content-Type: application/json

Request Body

{
   "orgExternalId": "your-org-external-id", 
   "clientExternalId": "your-client-external-id", 
   "userExternalId": "your-user-or-server-user-externalid", 
   "orgApiKey": "your-org-api-key"
}

Success — 200 OK

{"success": true, "token": "eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9..."}

The token is valid for 60 minutes. Reuse it across many generate calls; re-authenticate when it expires.

curl -s -X POST https://dataconnect.genrocket.com/daas/login \ -H "Content-Type: application/json" \ -d '{ "orgExternalId": "your-org-external-id", "clientExternalId": "your-client-external-id", "userExternalId": "youruser-external-id", "orgApiKey": "your-org-api-key" }'```

### 8.2 Generate Data — `POST /daas/generate`

Authenticated. Pass the JWT in the **`X-Daas-Token`** header.

```http
POST /daas/generate HTTP/1.1
Host: dataconnect.genrocket.com
Content-Type: application/json
X-Daas-Token: <jwt-from-login>

Top-level fields

Attribute Object

NOTE: Per-attribute resolution order: explicit generator wins → else listOfOptions or regex → else the LLM infers from name , dataType , and description .

Success — 200 OK : the body is a JSON array of record objects (one object per row). It is not wrapped in an envelope:

[
  { 
    "customer_id": "8f14e45f...", 
    "first_name": "Ava", 
    "email":"ava@example.com" 
  }, 
  { 
    "customer_id": "c9f0f895...", 
    "first_name": "Liam",
    "email": "liam@example.com" 
  }
]

Discovery — GET /daas/industries and GET /daas/generators

Anonymous (no token). Use these to discover valid values before building requests.

HTTP Request

GET /daas/industries

Request Body

{ "industries": ["Banking", "Healthcare", "Insurance", "NO_INDUSTRY"] }

HTTP Request

GET /daas/generators

Request Body

{
  "generators": [ 
    { 
      "name": "UUIDGen", 
      "shortDescription": "Generates UUIDs", 
      "description": "..." 
    }, 
    { 
      "name": "FirstNameGen",
      "shortDescription": 
      "Generates first names", 
      "description": "..." 
     } 
  ]
}

curl -s https://dataconnect.genrocket.com/daas/industriescurl -s
https://dataconnect.genrocket.com/daas/generators```
---
## 9. Generation Examples (Cookbook)

All examples assume `export TOKEN=<jwt-from-login>`.

### 9.1 Explicit generators
```bash
curl -s -X POST https://dataconnect.genrocket.com/daas/generate \ -H "Content-Type: application/json" -H "X-Daas-Token: $TOKEN" \ -d '{ "domain": "Customer", "industry": "Banking", "loopCount": 3, "attributes": [ { "name": "customer_id", "dataType": "string", "generator": [{ "name": "UUIDGen" }] }, { "name": "first_name", "dataType": "string", "generator": [{ "name": "FirstNameGen" }] } ] }'```

### 9.2 LLM-inferred attributes (no explicit rules)

Provide a `description`; the embedded LLM picks an appropriate generator.

```json
{
"domain": "Customer", "industry": "Healthcare", "loopCount": 5, "attributes": [ { "name": "patient_name", "dataType": "string", "description": "Full name of a patient" }, { "name": "blood_group", "dataType": "string", "description": "ABO blood group, e.g. O+, A-" } ]}

Enumerated value pool ( listOfOptions )

{
  "domain": "Account",
  "industry": "Banking",
  "loopCount": 4,
  "attributes": [
    {
      "name": "account_type",
      "dataType": "string",
      "listOfOptions": [
        "CHECKING",
        "SAVINGS",
        "CREDIT"
      ]
    },
    {
      "name": "currency",
      "dataType": "string",
      "listOfOptions": [
        "USD",
        "EUR",
        "INR"
      ]
    }
  ]
}

Pattern-constrained values ( regex )

{
  "domain": "Customer",
  "loopCount": 3,
  "attributes": [
    {
      "name": "email",
      "dataType": "string",
      "regex": "[a-z]{5,8}@example\\.com"
    },
    {
      "name": "us_zip",
      "dataType": "string",
      "regex": "[0-9]{5}(-[0-9]{4})?"
    }
  ]
}

Mixed schema with industry context

{
  "domain": "Transaction",
  "industry": "Banking",
  "context": "Domestic wire transfers for retail banking customers",
  "loopCount": 100,
  "attributes": [
    {
      "name": "txn_id",
      "generator": [
        {
          "name": "UUIDGen"
        }
      ]
    },
    {
      "name": "amount",
      "dataType": "decimal",
      "description": "Transfer amount between 10 and 5000"
    },
    {
      "name": "status",
      "listOfOptions": [
        "PENDING",
        "SETTLED",
        "FAILED"
      ]
    },
    {
      "name": "iban",
      "dataType": "string",
      "description": "Valid-looking IBAN"
    }
  ]
}

File output via receivers

Include exactly one receiver to receive a downloadable file instead of a JSON array. The response is a binary attachment ( Content-Disposition: attachment ).

curl -s -X POST https://dataconnect.genrocket.com/daas/generate \ -H "Content-Type: application/json" -H "X-Daas-Token: $TOKEN" \ -o customers.json \ -d '{ "domain": "Customer", "industry": "Banking", "loopCount": 100, "attributes": [ { "name": "customer_id", "generator": [{ "name": "UUIDGen" }] } ], "receivers": [ { "receiverName": "JSONFileReceiver", "parameters": { "fileName": "customers.json" } } ]
}'```

> Omit `receivers` entirely to get the inline JSON array. More than one receiver is rejected (`RECEIVERS_TOO_MANY`).

---

## 10. Complete Error Catalog
Every error returns the same shape:

```json
{ "success": false, "errorCode": "DAAS_TOKEN_EXPIRED", "message": "Authentication token expired" }

NOTE: Always branch on the success field, not the HTTP status alone. Quota outcomes are deliberately returned with HTTP 200 and success: false so they read as logical (not transport) failures.

MCP Server Integration

For AI agents and LLM tooling, DataConnect is exposed as a Model Context Protocol (MCP) server.

Every MCP Request must carry: 

Authorization: Bearer <jwt-from-login>

Error Codes

Authentication & Login ( POST /daas/login )

Org / Client / User Validation

Token & Session ( POST /daas/generate )

Generate Request Validation

Quota (returned as HTTP 200, success:false )

Exceeded vs. No-Active: *_QUOTA_EXCEEDED means the quota was used up.

*_NO_ACTIVE_QUOTA means there's nothing to consume because the configs were cancelled (or never created) — fix it by allocating/activating quota, not by waiting.

Server / catch-all