Summa icon

Summa

Consume Summa API (v.0.1.7)
Join our community

Actions182

Overview

This node integrates with the Summa API to perform various operations on telecom-related resources. Specifically, for the IMSI resource and the Edit IMSI operation, it allows users to update or modify IMSI records in the backend system managed by Summa.

Typical use cases include:

  • Updating roaming profiles or coverage settings for a subscriber's IMSI.
  • Modifying external identifiers linked to an IMSI.
  • Adjusting mobile station categories or other IMSI-specific attributes.

For example, a telecom operator might use this node to update the roaming profile of a subscriber’s IMSI after a plan change or to add new external identifiers for tracking purposes.

Properties

Name Meaning
Imsi The IMSI (International Mobile Subscriber Identity) string identifying the subscriber to edit.
Send Json Boolean flag indicating whether to send raw JSON data directly or use structured fields.
Json Data Raw JSON data to send when Send Json is true; represents the full payload for the IMSI update.
Additional Fields Collection of optional structured fields used when Send Json is false, including:
- Roaming Profile String specifying the roaming profile to assign to the IMSI.
- Map Screening Name String representing the map screening name associated with the IMSI.
- Delta Roaming Profile String for delta roaming profile adjustments.
- Mobile Station Category Number indicating the category of the mobile station.
- External Identifiers Unique Multiple entries each containing: Id (number), External Identifier (string), External Identifier Type (string), Trace Active (boolean). Used to uniquely identify external references.
- Default External Identifier Single entry with fields: Id, External Identifier, External Identifier Type, Trace Active. Represents the default external identifier for the IMSI.
- Enhanced Coverage String describing enhanced coverage options for the IMSI.

Output

The node outputs JSON data representing the response from the Summa API after attempting to edit the IMSI. This typically includes confirmation of the updated IMSI record, any error messages, or status information returned by the API.

If binary data were involved (not indicated here), it would represent files or media related to the IMSI, but this node focuses on JSON data only.

Dependencies

  • Requires an API key credential for authenticating with the Summa API.
  • Uses HTTP requests to communicate with the Summa backend service.
  • The node depends on internal helper classes and methods for request execution and response handling.
  • No additional environment variables are explicitly required beyond the API credential.

Troubleshooting

  • Invalid IMSI format: Ensure the IMSI string is correctly formatted as per telecom standards.
  • Authentication errors: Verify that the API key credential is valid and has necessary permissions.
  • Malformed JSON: When using Send Json with raw JSON input, ensure the JSON is well-formed and matches the expected schema.
  • Missing required fields: If not sending raw JSON, make sure all mandatory fields are provided in the Additional Fields collection.
  • API errors: Check the response message for specific error codes or messages from the Summa API to diagnose issues like invalid parameters or server errors.

Links and References

Discussion