Getting Started

DoubleDino Proxy allows developers to investigate real production data without accessing sensitive information.

Your platform team provides:

• DoubleDino URL.
• API key.
• Supported data source information.

Once connected, you can query data using the native syntax of the underlying data source.

How it works

Your query runs against the real data source.

The response is transformed before it is returned.

This means you can:

• Find real production issues.
• Use real identifiers.
• Understand relationships.
• Debug application behaviour.

Without receiving the original sensitive values.

Check the connection

Before querying data, verify the DoubleDino instance.

curl -G "http://localhost:8080/meta" \
  -H "x-api-key: your-api-key"

Example response:

{
  "status": "online",
  "type": "postgres"
}

The response shows:

• Current service status.
• Connected data source type.

Your first query

The query endpoint depends on the connected data source.

For SQL databases, use the database's normal query syntax.

Example PostgreSQL:

curl -G "http://localhost:8080/query" \
  --data-urlencode "q=SELECT * FROM orders WHERE id=1" \
  -H "x-api-key: your-api-key"

Example response:

{
  "id": 1,
  "order_uid": "Qm8x92Lk",
  "status": "processing",
  "customer_id": 38192
}

The response represents the original data, but sensitive values have been transformed.

Debugging with real identifiers

A common workflow:

A customer reports:

Order KLP-X60SLVTFMK is stuck.

Instead of asking for a database export or direct production access, query the production record:

SELECT *
FROM orders
WHERE order_uid='KLP-X60SLVTFMK'

DoubleDino finds the record using the real value.

The response contains transformed values:

{
  "order_uid": "Qm8x92Lk",
  "status": "processing"
}

The relationship between records remains intact, allowing investigation without exposing the original data.

Query format

DoubleDino follows the native query style of the connected data source.

Supported examples:

Data source	Endpoint	Query format
PostgreSQL	/query	PostgreSQL SQL
MySQL	/query	MySQL SQL
MariaDB	/query	MariaDB SQL
MongoDB	/query	Collection + MongoDB filter
Redis	/redis	Key lookup
Logs	/logs	Line retrieval

Authentication

Every request requires:

x-api-key

Example:

-H "x-api-key: your-api-key"

The API key is provided by your platform administrator.

Next steps

Choose your data source:

• PostgreSQL
• MySQL
• MariaDB
• MongoDB
• Redis
• Logs