> For the complete documentation index, see [llms.txt](https://docs.nected.ai/nected-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.nected.ai/nected-docs/management-api/singed-token-api.md).

# Singed token API

**GET** `/dev/v1/signed-token`

Per `swagger-doc.json`: **Google login to the server.** Supply **`Nected-API-Key`** and query **`email`** (required). This operation has **no** `security` array in Swagger; the API key is a required **parameter** instead.

### Query parameters

| Name    | Required | Description                          |
| ------- | -------- | ------------------------------------ |
| `email` | Yes      | Email for which the token is issued. |

### Headers

| Header           | Required | Description     |
| ---------------- | -------- | --------------- |
| `Nected-API-Key` | Yes      | Nected API key. |

## Google login to the server.

> Google login to the server (per Swagger). Supply \*\*\`Nected-API-Key\`\*\* and query \*\*\`email\`\*\* for which the token is issued.\
> \
> \*\*200\*\* — \*\*\`code\`\*\* is typically \`success\`, \*\*\`message\`\*\* e.g. \`Success.\`, and \*\*\`data.signedURL\`\*\* is the full redirect URL (includes signed token and optional \`redirect=\` query).

```json
{"openapi":"3.0.3","info":{"title":"Nected Dev V1 — Signed token","version":"1.0"},"tags":[{"name":"DevV1","description":"Development workspace APIs."}],"servers":[{"url":"https://api.nected.ai","description":"Production"}],"paths":{"/dev/v1/signed-token":{"get":{"operationId":"getDevV1SignedToken","tags":["DevV1"],"summary":"Google login to the server.","description":"Google login to the server (per Swagger). Supply **`Nected-API-Key`** and query **`email`** for which the token is issued.\n\n**200** — **`code`** is typically `success`, **`message`** e.g. `Success.`, and **`data.signedURL`** is the full redirect URL (includes signed token and optional `redirect=` query).","parameters":[{"name":"Nected-API-Key","in":"header","required":true,"description":"Nected API key.","schema":{"type":"string"}},{"name":"email","in":"query","required":true,"description":"Email for token issued.","schema":{"type":"string"}}],"responses":{"200":{"description":"OK","content":{"application/json":{"schema":{"$ref":"#/components/schemas/SignedTokenSuccessResponse"}}}},"400":{"description":"Bad Request","content":{"application/json":{"schema":{"$ref":"#/components/schemas/Response"}}}},"500":{"description":"Internal Server Error","content":{"application/json":{"schema":{"$ref":"#/components/schemas/Response"}}}}}}}},"components":{"schemas":{"SignedTokenSuccessResponse":{"type":"object","required":["code","message","data"],"properties":{"code":{"type":"string"},"message":{"type":"string"},"data":{"$ref":"#/components/schemas/SignedTokenData"}}},"SignedTokenData":{"type":"object","description":"Payload returned in `data` on success.","required":["signedURL"],"properties":{"signedURL":{"type":"string","format":"uri","description":"App redirect URL containing the signed token; may include a `redirect=` query parameter for post-login navigation."}}},"Response":{"type":"object","description":"Standard API wrapper (`response.Response` in Swagger 2 definitions).","properties":{"code":{"type":"string"},"message":{"type":"string"},"data":{"type":"object","nullable":true},"pageNo":{"type":"integer"},"pageSize":{"type":"integer"},"totalCount":{"type":"integer"},"totalPages":{"type":"integer"}}}}}}
```

### Example

```bash
curl -X GET "{{NECTED_BASE_URL}}/dev/v1/signed-token?email=user@example.com" \
  -H "accept: application/json" \
  -H "Nected-API-Key: <YOUR_API_KEY>"
```


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.nected.ai/nected-docs/management-api/singed-token-api.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.