> For the complete documentation index, see [llms.txt](https://docs.eseye.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.eseye.com/api-reference/api-reference-pt-br/api-de-sim/sim-attribute/view-a-specific-sim-attribute.md).

# View a specific SIM attribute

Retrieves a SIM attribute by its ID.

```json
{"openapi":"3.1.0","info":{"title":"AnyNet SIM API","version":"2.0.0"},"tags":[{"name":"SIM attribute"}],"servers":[{"url":"https://sim.api.anynetiot.com","description":"Production"}],"security":[{"bearerAuth":[]}],"components":{"securitySchemes":{"bearerAuth":{"type":"http","scheme":"bearer","bearerFormat":"JWT","description":"An OAuth 2.0 client credentials access token, sent as `Authorization: Bearer <token>`.\n\nRequest the token from `https://eseye-idp-prod.auth.eu-west-1.amazoncognito.com/oauth2/token` using the client ID and client secret Eseye supplied. Tokens expire after one hour."}},"parameters":{"iccId":{"name":"iccId","in":"path","required":true,"description":"The ICC ID of the SIM.","schema":{"type":"string"}},"iccAttributeId":{"name":"iccAttributeId","in":"path","required":true,"description":"The unique identifier for the SIM attribute.","schema":{"type":"integer"}},"startDate":{"name":"startDate","in":"query","required":false,"description":"Filter history records from this date onwards, inclusive, in the format `YYYY-MM-DD HH:mm:ss`.","schema":{"type":"string","format":"date-time"}},"stopDate":{"name":"stopDate","in":"query","required":false,"description":"Filter history records up to this date, inclusive, in the format `YYYY-MM-DD HH:mm:ss`.","schema":{"type":"string","format":"date-time"}}},"schemas":{"SimAttribute":{"type":"object","properties":{"iccAttributeId":{"type":"integer","description":"The unique identifier for the attribute."},"iccId":{"type":"string","maxLength":20,"description":"The SIM the attribute belongs to."},"attribute":{"type":"string","maxLength":48,"description":"The attribute name. Names cannot contain spaces."},"value":{"type":"string","maxLength":255,"description":"The attribute value. Can be an empty string, but not `null`."},"status":{"$ref":"#/components/schemas/RecordStatus"}},"description":"A name/value pair attached to a SIM."},"RecordStatus":{"type":"string","description":"Whether the record is still attached to its parent object.\n\n| Value | Meaning |\n| --- | --- |\n| `active` | The record is attached to the parent object. |\n| `deleted` | The record is no longer attached to the parent object. |","enum":["active","deleted"]},"Error":{"type":"object","properties":{"errorCode":{"type":"integer","description":"The Eseye error code.\n\n| Code | Meaning |\n| --- | --- |\n| `6001` | Your service account does not have permission for this operation. |\n| `6002` | An object referenced in the request does not exist. |\n| `6003` | The request method is wrong or missing. |\n| `6004` | The server could not be reached. Check the request URL and your connection. |\n| `6006` | The request is malformed. A mandatory field is missing, a data type is wrong, a value is too long, or the JSON is invalid. |\n| `6007` | You do not have permission to make this status transition. |"},"errorTag":{"type":"string","description":"A short error name. Contains no spaces."},"message":{"type":"string","description":"A short description of the error."},"additionalDetails":{"type":"object","description":"Names the object that could not be resolved, or lists the fields that failed validation."}},"description":"An error returned by the API."}},"responses":{"BadRequest":{"description":"The request contained an invalid parameter. `additionalDetails` lists the fields that failed validation.","content":{"application/json":{"schema":{"$ref":"#/components/schemas/Error"}}}},"Forbidden":{"description":"The token is valid, but the service account does not have permission for this operation.","content":{"application/json":{"schema":{"$ref":"#/components/schemas/Error"}}}},"NotFound":{"description":"An entity referenced in the request does not exist. The `message` and `additionalDetails` name what could not be resolved.","content":{"application/json":{"schema":{"$ref":"#/components/schemas/Error"}}}}}},"paths":{"/api/v2/sim/{iccId}/attribute/{iccAttributeId}":{"get":{"summary":"View a specific SIM attribute","operationId":"view-specific-sim-attribute","tags":["SIM attribute"],"parameters":[{"$ref":"#/components/parameters/iccId"},{"$ref":"#/components/parameters/iccAttributeId"},{"$ref":"#/components/parameters/startDate"},{"$ref":"#/components/parameters/stopDate"}],"responses":{"200":{"description":"The requested SIM attribute.","content":{"application/json":{"schema":{"$ref":"#/components/schemas/SimAttribute"}}}},"400":{"$ref":"#/components/responses/BadRequest"},"403":{"$ref":"#/components/responses/Forbidden"},"404":{"$ref":"#/components/responses/NotFound"}},"description":"Retrieves a SIM attribute by its ID."}}}}
```


---

# 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, and the optional `goal` query parameter:

```
GET https://docs.eseye.com/api-reference/api-reference-pt-br/api-de-sim/sim-attribute/view-a-specific-sim-attribute.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.
