Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support for Custom Port, IP, and Reading Received SMS (Without Sending) #14

Closed
Lolig4 opened this issue Dec 28, 2024 · 5 comments
Closed
Labels

Comments

@Lolig4
Copy link

Lolig4 commented Dec 28, 2024

Hi, I’d like to configure the Android SMS Gateway app to:

Use a local IP with a custom port (e.g., 53333):
I want to access the API via my local IP instead of the default API web service. Could you add an option to specify a custom port and IP for the service?

Read received SMS messages:
I’m only interested in reading received SMS messages, not sending messages. Can you provide a way to directly read the received messages via the API without sending any?

Thanks

@capcom6
Copy link
Member

capcom6 commented Dec 28, 2024

Hello!

Thank you for your feature request. Let me address your points:

  1. Custom Port and Local IP:

  2. Reading Received SMS Messages:

If you decide to use the version from the PR, you can request messages from the inbox for a custom period in Local Server mode. Follow these steps:

  1. Set up your webhook receiver for sms:received messages.
  2. Start the app in Local Server mode.
  3. Register the webhook URL as described at https://docs.sms-gate.app/getting-started/webhooks/
  4. Make a POST request to http://<device-ip>/messages/inbox/export with a JSON payload like:
    {
      "since": "2024-01-01T00:00:00.000",
      "until": "2024-12-31T23:59:59.999"
    }
  5. You will receive an sms:received webhook for each message in the selected period. Please note that the order of messages is not specified.

Please be aware that the version from the PR is not final, and features may change before the official release.

Copy link

This issue is stale because it has been open for 7 days with no activity.

2 similar comments
Copy link

This issue is stale because it has been open for 7 days with no activity.

Copy link

This issue is stale because it has been open for 7 days with no activity.

@github-actions github-actions bot added the stale label Jan 31, 2025
Copy link

github-actions bot commented Feb 7, 2025

This issue was closed because it has been inactive for 7 days since being marked as stale.

@github-actions github-actions bot closed this as completed Feb 7, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants