Skip to content

Commit 3a8e32a

Browse files
committed
Fix tags in Android guide.
1 parent 2f0f8fd commit 3a8e32a

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

_includes/android/push-notifications.md

+2-2
Original file line numberDiff line numberDiff line change
@@ -476,7 +476,7 @@ Basically, you will need to run the same push query you're using for your target
476476

477477
The REST API is quite easy to use for this sort of purpose as you can easily recreate the push query using the information provided in your push notification logs. If you look closely at the “Full Target” value in your push campaign log item, you may notice that it matches the query format for a REST API query. You can grab an example of what a [REST API query](/docs/rest#queries-constraints) over `ParseInstallation`s would look like from the REST API docs. Don't forget to use the `X-Parse-Master-Key` header to ensure that the Master Key is used to run this query.
478478

479-
<pre><code class="bash">
479+
```bash
480480
# Query over installations
481481
curl -X GET \
482482
-H "X-Parse-Application-Id: {YOUR_APPLICATION_ID}" \
@@ -489,7 +489,7 @@ https://api.parse.com/1/installations
489489

490490
If you type the above into a console, you should be able to see the first 1,000 objects that match your query. Note that constraints are always ANDed, so if you want to further reduce the search scope, you can add a constraint that matches the specific installation for your device:
491491

492-
<pre><code class="bash">
492+
```bash
493493
# Query over installations
494494
curl -X GET \
495495
-H "X-Parse-Application-Id: {YOUR_APPLICATION_ID}" \

0 commit comments

Comments
 (0)