Classes

The MNFAccount class encapsulates account json data from the Meniga PFM server in an object.

An account should not be directly initialized but instead should be constructed with data from the server. The response from the server will be automatically converted to an MNFAccount object.

An account has two mutable properties which can be changed. If you change said properties you should remember to save the account so your changes will be saved on the server. If you do not save your changes they may be overwritten if you update the account with server data. A boolean property ‘isDirty’ keeps track of unsaved changes, which can then be reverted.

The MNFAccountAuthorizationType class represents an account authorization type.

An account authorization type should not be directly initialized but fetched from the server through MNFAccount.

The MNFAccountType class represents account types.

An account type should not be initialized directly but fetched from the server through MNFAccount.

The MNFAccountHistoryEntry class represents account history data.

An account history entry should not be initialized directly but rather fetched from the server through MNFAccount.

The MNFAccountType class represents a realm account type.

A realm account type should not be directly initialized but fetched from the server through MNFAccount.

The MNFBudget class represents a budget object with serialized json data from the server and methods to interact with the budget api.

The MNFBudgetEntry class represents a single budget entry.

The MNFBudgetFilter class represents a filter object used to fetch budgets filterd by budget entries from the server.

@abstract An MNFCategoryType object has an identifier and name. The identifier property is an NSNumber inherited from the MNFObject and is used as a unique identifier. The name better describes the category type and its function.

An MNFCategory encapsulates category json data from the server in an object.

A category should not be directly initialized but instead should be constructed with data from the server. The response from the server will be automatically converted to an MNFCategory object.

The MNFCategoryScore class represents the probability of a category applying to a particular merchant or transaction.

The MNFChallenge class represents a challenge.

The MNFCustomChallenge class represents a custom challenge created by the user.

The MNFGlobalChallenge represents a global spending challenge generated by the server.

The MNFSpendingChallenge represents a suggested challenge generated by a server admin.

The MNFFeed class encapsulates the user feed json data in an object.

A feed should not be directly initialized but instead should be constructed with data from the server. The response from the server will be automatically converted to an MNFFeed object.

The MNFFeedItem class encapsulates feed item json data from the server in an object.

A feed item should not be directly initialized but instead should be constructed with data from the server. The response from the server will be automatically converted to an MNFFeedItem object.

The MNFFeedItemGroup class represents a list of feed items in a feed grouped together by date.

A feed item group is automatically created when performing grouping on a feed.

The MNFMerchant class represents all information of a merchant.

The MNFMerchantAddress represents all address information for a merchant.

MNFNetworth represents the main networth class from which you fetch main info and lists with Networth information. Networth accounts

The MNFObject class is the superclass for all objects in the Meniga SDK.

The superclass handless internal operations of the objects and state handling.

The MNFAccountSyncStatus represents sync status information for an account in a realm being synchronized.

An account sync status should not be directly initialized.

The MNFRealmSyncResponse represents information when syncing to a financial data realm.

A sync response should not be directly initialized but fetched from the server through MNFSynchronization.

The MNFSyncAuthRequiredParameter represents parameters required by the user for synchronization.

A sync auth required parameter should not be directly initialized.

The MNFSyncAuthenticationChallenge represents information on an authentication challenge the user receives during synchronization.

A sync authentication challenge should not be directly initialized.

The MNFSynchronization class encapsulates synchronization data from the server in an object.

A synchronization object should not be directly initialized but rather fetched through the server when performing synchronization.

The MNFTag class encapsulates tag json data from the server in an object.

A tag should not be created directly. It is instead created as part of a comment on a transaction using a hashtag (#) prefix.

The MNFComment class encapsulates comment json data from the server in an object.

A comment should not be initialized directly but rather fetched from the server through fetching transactions. A comment can be created by posting a comment to a transaction.

The MNFTransaction class encapsulates transaction json data from the server in an object.

A transaction should no be directly initialized but instead should be constructed with data from the server. The response from the server will be automatically converted to an MNFTransaction object.

The MNFTransactionFilter class encapsulates a transaction filter json data in an object.

A transaction filter should be initialized directly and used when fetching transactions using a filter.

The MNFTransactionGroup class represents a list of transactions in a transaction page grouped together by either date or category.

A transaction group is automatically created when performing grouping on a transaction page.

The MNFTransactionPage class encapsulated transaction page json data form the server in an object.

A transaction page should no be directly initialized but instead should be constructed with data from the server. The response from the server will be automatically converted to an MNFTransactionPage object.

The MNFTransactionRule class encapsulates transaction rule json data from the server in an object.

A transaction rule can be initialized directly or fetched from the server. When creating a new transaction rule populate properties accordingly before calling save. This will create the rule on the server and assign it a userId and the requisite dates. Use the applyOnExisting property to indicate whether this rule should apply to existing transactions.

The MNFTransactionSeries class encapsulates transaction series json data in an object.

A transaction series should not be directly initialized but fetched from the server. Transaction series represents transaction aggregation.

The MNFTransactionSeriesFilter class is used to construct a transaction series request.

A transaction series filter should be directly initialized and used when fetching transaction series.

The MNFTransactionSplitAction class encapsulates split action json data from the server in an object.

A split action can be directly initialized or initialized when fetching a transaction rule from the server.

The MNFUpcoming represents information on upcoming transactions created by the user.

The MNFUpcomingBalance class contains information of upcomings from today in a list of dates with balance.

The MNFUpcomingBalanceDate class containg information on projected balance entries when fetching upcoming balance.

The MNFUpcomingComment class contains information on a comment made to an upcoming transaction.

The MNFUpcomingDetails class contains detailed information on an upcoming transaction such as invoice and payment information.

The MNFUpcomingInvoice class contains information on an invoice linked to an upcoming transaction.

The MNFUpcomingPattern class represents a Cron expression that recurring patterns are scheduled from.

The MNFUpcomingReconcileScore class contains information on how well a suggested upcoming transaction matches a real transaction.

The MNFUpcomingScheduledPayment class contains information on scheduled payments.

The MNFUpcomingThreshold class contains information on a threshold the user has set for an account.

The MNFUserEvent class encapsulates user event json data from the server in an object.

A user event should not be directly initialized. It is created by fetching a user feed using MNFFeed. A user event will be created as part of a feed data.

The MNFRealmUser class represents a user’s realm information.

A realm user should not be directly initialized but fetched from the server.

The MNFUser object encapsulates a user profile json data from the server in an object.

A user should not be directly initialized but instead should be constructed with data from the server. The response from the server will be automatically converted to an MNFUser object.

The MNFUserProfile class represents user profile information in an object.

A user profile should not be directly initialized but fetched from the server.

The MNFJob class acts as a wrapper for the Bolts framework developed by Facebook.

A job contains a Bolts task and a task completion source both of which can be used to initialize a job. Additionally a job contains a reference to the URL request used to carry out server requests from the MNF framework. Therefore a server request can be cancelled if it has not completed by cancelling the job.

A job should not be directly initialized but should rather use a Bolts task tompletion source to initialize with.