Openemr rest api does not seem to be starting/listening

hanksterr7 · August 14, 2021, 3:52pm

One suggestion, so others don’t make such dumb mistakes:
I got my info on how to use the api’s from this page

openemr/openemr/blob/master/API_README.md

# OpenEMR REST API Documentation

## Overview

Easy-to-use JSON-based REST API for OpenEMR. All code is done in classes and separate from the view to help with codebase modernization efforts. FHIR is also supported, see FHIR API documentation [here](FHIR_README.md)

## Implementation

REST API endpoints are defined in the [primary routes file](_rest_routes.inc.php). The routes file maps an external, addressable
endpoint to the OpenEMR controller which handles the request, and also handles the JSON data conversions.

```php
"POST /api/patient" => function () {
    RestConfig::authorization_check("patients", "demo");
    $data = (array) (json_decode(file_get_contents("php://input")));
    $return = (new PatientRestController())->post($data);
    RestConfig::apiLog($return, $data);
    return $return;
}
```

This file has been truncated. show original

All of the examples mention localhost:8300, and I didn’t see much obvious on that page that says the examples are tuned for the docker install
If the examples said
curl -X POST ‘http://[openemr root path]/apis/default/api/facility’
instead of
curl -X POST ‘http://localhost:8300/apis/default/api/facility’
that would have been much clearer

Similarly, in several threads (such as Cannot get API to work), I’ve seen @brady.miller give example api calls that specify localhost and a port and not add a comment such as “replace localhost:8300 with your domain name and path to the openemr root”. I know, that should be obvious, but there are lots of newbies diving into this
Thanks