coreyman

It appears the problem cleared itself, however support emails to our support@ address are now mysteriously not importing and we haven't changed anything regarding that.

You wouldn't need someone familiar with blesta functions to create the API. Just someone that is familiar creating API's. I use freelancer.com for work that I hire out.

Oh yeah I'm aware, I was just pointing him in the right direction

I found this -
So I tried accessing an endpoint via the attached image method in postman and it looks like we are on the right track. Looks like the arguments are as follows -
"contact_info" => $contact_info, "amount" => $amount, "currency" => $currency, "invoice_amounts" => $invoice_amounts, "options" => $options, "gateway_id" => $gateway_id This method and docblock can be found in \components\gateway_payments\gateway_payments.php
    /**      * Returns an array of HTML markup used to render capture and pay requests for non-merchant gateways      *      * @param array $contact_info An array of contact info including:      *  - id The contact ID      *  - client_id The ID of the client this contact belongs to      *  - user_id The user ID this contact belongs to (if any)      *  - contact_type The type of contact      *  - contact_type_id The ID of the contact type      *  - first_name The first name on the contact      *  - last_name The last name on the contact      *  - title The title of the contact      *  - company The company name of the contact      *  - address1 The address 1 line of the contact      *  - address2 The address 2 line of the contact      *  - city The city of the contact      *  - state An array of state info including:      *      - code The 2 or 3-character state code      *      - name The local name of the country      *  - country An array of country info including:      *      - alpha2 The 2-character country code      *      - alpha3 The 3-cahracter country code      *      - name The english name of the country      *      - alt_name The local name of the country      *  - zip The zip/postal code of the contact      * @param float $amount The amount to charge this contact      * @param string $currency The current to charge      * @param array $invoice_amounts An array of invoices, each containing:      *  - id The ID of the invoice being processed      *  - amount The amount being processed for this invoice (which is included in $amount)      * @param array $options An array of options including:      *  - description The Description of the charge      *  - return_url The URL to redirect users to after a successful payment      *  - recur An array of recurring info including:      *      - start_date The date/time in UTC that the recurring payment begins      *      - amount The amount to recur      *      - term The term to recur      *      - period The recurring period (day, week, month, year, onetime) used      *        in conjunction with term in order to determine the next recurring payment      * @param int $gateway_id The ID of the nonmerchant gateway to fetch,      *  if null will return all nonmerchant gateways for the currency      * @return array An array of HTML, indexed by the gateway name      */  

This is just a guess, but if you look in \projectfolder\vendors\components\gateways\nonmerchant\paypal_payments_standard\paypal_payments_standard.php you will find 
PaypalPaymentsStandard extends NonmerchantGateway It looks like you are required to have a Blesta invoice to pay to use this gateway, so you will probably need to generate an invoice first.
On line 232 there is buildProcess where I found this information. It looks like it's building the request to paypal. Maybe someone else can shed some more light.

Ahh ok I didn't know cron was creating those files. I'll change this. Thank you!

You would need to develop this functionality into blesta, or create your own API. Currently the blesta api offers full access to all functions of blesta so your customer would have access to everything, including other customers data. Administrators do not have have granular controls on what access API users have at the endpoints, and probably never will due to the way the blesta api works.

http://source-docs.blesta.com/class-Clients.html
Looks like you need to use class Clients.
getByUserId( integer $user_id, boolean $get_settings = false ) Fetches a client with contact details of the primary account holder Parameters $user_id integer $user_id The ID of the user Then you can delete by client id
#delete( integer $client_id )  

http://source-docs.blesta.com/class-Clients.html
Looks like you need to use class Clients.
getByUserId( integer $user_id, boolean $get_settings = false ) Fetches a client with contact details of the primary account holder Parameters $user_id integer $user_id The ID of the user Then you can delete by client id
#delete( integer $client_id )  

Yes, because my mailserver puts incoming mail in the root of the mailbox. It requires no box name. By default outlook looks here for mail, you have to manually configure outlook to look in .INBOX. I think .INBOX is a 'cpanel' constructed way of configuring a mail server.

Thanks! Will be backing up everything prior to import.

If anyone wants to know how much an owned unbranded license is worth second hand. I just paid $150+support and updates for a year from @evolvewh

If anyone wants to know how much an owned unbranded license is worth second hand. I just paid $150+support and updates for a year from @evolvewh

I know how obvious that is, but I didn't even pay attention to it

mcrypt is not available by default for php7.3 so you have to use PECL to install it. I followed the tutorial here (Even though it says php7.2)
https://lukasmestan.com/install-mcrypt-extension-in-php7-2/

We've been WHMCS users for well over 8 years and today we took the leap to Blesta. We will be integrating it with our new platform and slowly moving clients over in 2019. We have grown so tired of the price increases and code refactors over at WHMCS with no real added value for us.

We've been WHMCS users for well over 8 years and today we took the leap to Blesta. We will be integrating it with our new platform and slowly moving clients over in 2019. We have grown so tired of the price increases and code refactors over at WHMCS with no real added value for us.

We've been WHMCS users for well over 8 years and today we took the leap to Blesta. We will be integrating it with our new platform and slowly moving clients over in 2019. We have grown so tired of the price increases and code refactors over at WHMCS with no real added value for us.

mcrypt is not available by default for php7.3 so you have to use PECL to install it. I followed the tutorial here (Even though it says php7.2)
https://lukasmestan.com/install-mcrypt-extension-in-php7-2/

All of these systems are made to be customized. With that in mind, I would probably be interested in buying your license.

We've been WHMCS users for well over 8 years and today we took the leap to Blesta. We will be integrating it with our new platform and slowly moving clients over in 2019. We have grown so tired of the price increases and code refactors over at WHMCS with no real added value for us.

We've been WHMCS users for well over 8 years and today we took the leap to Blesta. We will be integrating it with our new platform and slowly moving clients over in 2019. We have grown so tired of the price increases and code refactors over at WHMCS with no real added value for us.

Stripe is continuing to support hosting businesses. Just got in contact with them.

Stripe is continuing to support hosting businesses. Just got in contact with them.

Yes, take a look at Invoices::add, which you can call via the API.